No Human Input Required

  • 10 January 2022
  • 0 replies
  • 46 views

Userlevel 4
Badge +8

No human input required means that no human involvement is expected during the bot's execution. Click the link below matching the Solution Pattern Model for your use case for details on an appropriate bot template/framework, as well as the specific least privilege roles needed for execution. How will your bot be executed?

 


 

Unattended

There are 3 Solution Patterns for running Unattended Bots:

 

Run Remote on Demand

  • Initiating a bot run directly from the Control Room ad-hoc to run on one or more unattended bot runners

 

 

Run Remote via API

  • Initiating a bot run using the Control Room API to run on one or more unattended bot runners

 

 

Run Remote via Schedule

  • A bot run that is initiated/configured using the Control Room scheduling capabilities to run on one or more unattended bot runners


 

Attended

There are 2 Solution Patterns for running Attended Bots:

 

Run Local on Demand

  • Initiating a bot run directly from the Control Room ad-hoc to run on the local machine

 

 

Run Local via Event Trigger

  • A bot run that is initiated from an event trigger, where the bot runs locally on the user's workstation

 

 


 

Unattended

There are 5 Solution Patterns for running Unattended Bots with WLM:

 

Run Remote on Demand with WLM

  • a bot run that is initiated using the Run Task Bot functionality of the Control Room to execute a bot 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

  • a bot run 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 a bot run directly from the Control Room ad-hoc to run a bot that will execute on the local device that adds Work Items to a Queue

 

 

Run Local via Event Trigger with WLM

  • A bot run 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 bot modeling options and how to apply the systematic solution approaches of the Solution Pattern Modeling framework to simplify your bot-building processes.


0 replies

Be the first to reply!

Reply