haylebop

After working with support we found out what the issue was!

The "Delete Notification" required waiting on the web app to run that, and the workflow got out of step and failed.

Fixed this by moving "Delete Notification" to the end of the workflow. Multiple scripts run with Custom fields and variables no problem!

Im not sure that is possible currently with workflows.
Ive setup patch polices applied to Sites, Orgs, or agent groups via "Server Admin" and "Configuration"
These also inherit from top down. Based on what agent installer file we give it will send the machine to the right group, Then the patch policy is applied.

Once thats complete, You should be able to setup the workflow to "Run assigned patch Policy".


 
Hope that helps!

After working with support we found out what the issue was!

The "Delete Notification" required waiting on the web app to run that, and the workflow got out of step and failed.

Fixed this by moving "Delete Notification" to the end of the workflow. Multiple scripts run with Custom fields and variables no problem!

nevermind figured it out

Hi folks,
I am seeing this trigger, System Registered, in the Automation > Workflows area. I'm imagining this trigger combined with the organization condition value can easily automate a series of actions to perform onboarding computers automatically. 
In testing, this works fabulously. However, it seems Pulseway RMM only allows one active workflow to use the 'System Registered' trigger. Understandable. I suppose I could use a single Workflow that uses the 'System Registered' trigger that cascades through all my clients. i.e. Organization Condition=ABC Customer: true/false > a false answer cascades to a new Organization Condition=XYZ Customer: true/false, etc, etc until a true result is found that kicks off the actions. This would quickly become difficult to manage, though I am considering it as I dont have any other options at the moment.
Looking for how you all have automated your on-boarding efforts? What are you doing that works for you? 

I am not a Pusleway user anymore, but there are a couple of ways you could do this.  You mention event ID, but I don't see any logic in your script to write an event ID to the event log.
However, that would probably be the easiest way, and then have Pulseway look for (and alert off of) that event entry.  I always set up a custom Event Log and then use my own codes so that I never have to worry about looking through logs with other stuff in it.  All my stuff goes to a custom log I set up.  
As far as your code, your logic seems, a bit off to me unless I'm just too tired lol, but your first if statement, your essentially saying if lastboot is BEFORE 14 days ago, SetCustomeFieldNo... Would you want that to be a yes, since that means it hasn't rebooted in over 14 days? I think your statements are backwards.  I assume your SetCustomField Yes would be used for if it's been up for over 14 days. Maybe I'm just reading it wrong.
I personally wouldn't bother with setting the custom fields. I would again, just write to whatever event log you want, with whatever event ID you want, set Pulseway to alert off that event ID, and then schedule your script to run once a day.  As soon as it runs and sees a machine over 14 days, it creates event log entry which Pulseway will then alert you to. 

Woo hoo! Thanks yall for continually adding and growing featuress!!!

Ok thanks for the confirmation Mark! Agreed!
 

I would make sure that all agents and pulseway remote control is fully updated, and try to find a common thread between them.
Are these on a specific network, machines fully up to date with windows updates, etc? 

If it was all having issues, I would think its a configuration or Pulseway error, but since only some are acting up it seems to be either something with those endpoints or with the network they are using. 
 
Following thread so let me know any further info, maybe i can help. 
 

As of right now, I do not believe there is any other way to move systems.  Permission enhancements across the board is something I'd like to see happen within Pulseway.  From script access (Scripts should have different access levels assigned to them so you can restrict certain scripts to a higher tier), to policies, to moving systems, etc.  As you build a team, permissions becomes extremely important.

You could try using workflows under Automation now.  Especially if you are trying to do something when a system is registered.  Set up a workflow with conditions you can match to specific clients, and then have that workflow add the tag. 

For our client security audits, and PEN testing events, we are required to disable NetBIOS on the network adapters.  The below script is what we run when an asset registers with Pulseway.
 
$key = "HKLM:SYSTEM\CurrentControlSet\services\NetBT\Parameters\Interfaces"
Get-ChildItem $key |
foreach { Set-ItemProperty -Path "$key\$($_.pschildname)" -Name NetbiosOptions -Value 2 -Verbose}

Going to bring this thread back to the top.  If anyone else feels that having the ability to input at run time a variable they declared as a custom field in their scripts, please upvote.  This is probably one of the single biggest improvements I want to see with Pulseway.  Custom variables should be able to be set to prompt at run for input.  We should also be able to set Customer level variables that are static and can be called in a given script.  
Here is the link to the feature request.  I did search and didn't find someone else asking about this, but I may have missed it. Either way, doesn't seem high on the list of votes so getting more attention to it would be great. 
https://pulseway.featureupvote.com/suggestions/189283/more-robust-input-and-site-variables

Ive been using workflows to emulate the automation flows I was used to in other RMMs. 

The first attached photo will trigger off an event Notification from our policy setting event filter, (all our managed systems have OEM licenses), Verify its the right event, via ID, or Name, or contents. and run a powershell script I have to pull the OEM key from the system and apply it. 
 
and the second gets triggered on high CPU notifications, adds 1 to a System custom field via a PS script and if it is over a value of 3 will email a ticket to our helpdesk. 

Hope this helps spur some ideas!