Workflows is a powerful, low-code IT orchestration platform that enables you to define step by step instructions of complex automations by utilizing resources such as Sensor, Remote Action and more.Use Workflows to automate routine tasks and troubleshoot common digital employee experience (DEX) issues. This minimizes the friction users encounter with company technology, improving overall productivity..
Automate common IT tasks with Workflows, such as:
And many more cases.
Note : Workflows is available as part of Endpoint Analytics and Available as Early Access. Windows Operating System is only supported.
Workflows are built using three main components: Sensors, Switch, and Actions. Lets explore what each one does.
Switch - User may need to deploy action in workflow using certain conditions defined in workflow. Switch can be used to define conditions for actions. Outcome of sensors can be used to define condition in Switch.
Complex condition require multiple AND and OR logical operators use in pattern definition. Add condition in case and define criteria pattern for it.
For instance, a Switch condition could check if free disk space is less than 10%. If yes, the workflow proceeds to an action to clean up files.
This can be configured similar to below.
To Create new workflow
The Workflow Builder interface provides a visual workspace to design and build your automated workflows.Interface contains five main elements.
When you add a stage to your workflow builder, a settings window will appear. This window allows you to configure the properties of the specific stage you've chosen.
SensorSensor lets you to get device attributes from endpoints. This output can be used in other stages of workflows.
To add Sensor as a Stage, drag and drop Sensor and enter the following details
Remote Actions allows you to execute actions targeted by workflow.
To add Remote Action as a Stage, drag and drop Remote Action and enter the following details
Switch allows branching workflows based on device attributes collected by Sensors. Agent evaluate cases in switch during workflow execution and decide further processing branch.
If no case are matching during evaluation, Workflow will stop running.
Based on Sensor output variable type, Criteria is supported.
To add Switch as a Stage, drag and drop Switch and enter the following details
End stage specifies end of workflow execution. It is required to have End stage at the end of every branch.
To add End as a Stage, drag and drop End and enter the following details
You can trigger workflow execution ondemand basis. You can initiate execution of Active workflow from console and will be deployed to devices during its start up or agent refresh cycle.
To manually run workflow
After initiating workflow run, Execution Details can be found for every workflow by clicking View Execution Details.
To grant user permissions for managing Workflow, follow these steps:
What devices are targeted when I run a workflow?
When you run a workflow from Endpoint Analytics, all endpoints listed under the Devices section are included as targets. Additionally, any newly onboarded devices will automatically process the latest workflow run.
Is it possible to deploy a workflow to a specific group of computers in Endpoint Analytics?
Currently, workflows are deployed to all computers managed within the Endpoint Analytics module. Targeting specific groups of devices is not supported at this time.
When does the agent process a workflow after it is deployed?
Once a workflow is run, the agent processes the workflow during its next refresh cycle or at startup, whichever occurs first.
When is a workflow run marked as complete?
A workflow run is considered complete when all targeted devices successfully process the workflow within the specified timeout period. The total timeout period is 90 minutes, with an additional 5 minutes allocated for each stage of the workflow after the run is initiated.
Why is a workflow run marked as failed?
A workflow run is marked as failed if no devices successfully complete the workflow within the designated timeout period. The timeout period is 90 minutes in total, with an additional 5 minutes allocated for each stage of the workflow after the run is initiated.
How many past workflow runs are stored in Endpoint Analytics?
A maximum of 30 workflow runs are stored for each workflow. This enables you to access and review the most recent workflow executions easily.
Thank you for your feedback!
Sorry about that!