No human input required means that no “human in the loop” is required - once invoked, these automations are designed to execute without human involvement/intervention. Click the link below matching the Solution Pattern Model for your use case for details on an appropriate automation template/framework, as well as the specific least privilege roles needed for execution. How will your automation be executed?
Unattended
There are 4 Solution Patterns for running Unattended Automations:
Run Remote on Demand
- Initiating an automation run directly from the Control Room ad-hoc to run on unattended runners.
Run Remote via API
- Initiating an automation using the Control Room API to run on one or more unattended runners/devices
Run Remote via API (Conversational)
- A ‘variation’ of ‘Run Remote via API’, this pattern involves invoking automation from an external “chatbot”
- The automation will be executed on one or more unattended runners/devices.
Run Remote via Schedule
- An automation that is initiated/configured using the Control Room scheduling capabilities to run on one or more unattended runners/devices.
- Usage: any time you need a process executed on a schedule.
Attended
There are 2 Solution Patterns for running Attended Automation:
Run Local on Demand
- Initiating an automation run directly from the Control Room ad-hoc to run on the local machine
Run Local via Event Trigger
- An automation that is initiated from an event trigger, run locally on the user's workstation
Workload Management (WLM)
There are 5 Solution Patterns for running Automations with WLM:
Run Remote on Demand with WLM
- an automation that is initiated using the Run Task Bot functionality of the Control Room to execute an automation that adds Work Items to a Queue
Run Remote via API with WLM
- using the Control Room API to add Work Items to a WLM Queue
Run Remote via Schedule with WLM
- an automation that is initiated/configured using the Control Room scheduling capabilities to execute and add Work Items to a WLM Queue
Run Local on Demand with WLM
- Initiating an automation directly from the Control Room that will execute on the local device that adds Work Items to a Queue
Run Local via Event Trigger with WLM
- An automation that is initiated from an event trigger where Work Items are added to a WLM queue
Not interested in these options? Go back to the Solution Pattern Modeling Framework homepage to get more details on additional automation modeling options and how to apply the systematic solution approaches of the Solution Pattern Modeling framework to simplify your automation-delivery processes.