Automation Pathfinder Program

No Human Input Required

  • 10 January 2022
  • 0 replies
  • 458 views
No Human Input Required
Userlevel 6
Badge +10

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

 

This pattern - one of the most simple - involves logging in to the Control Room to execute the automation when required. The automation will execute on their local device. 

 

In this pattern, the execution of the automation is ad-hoc or on-demand. Kindly note that the local device from which the user logs in to the Control Room will be ‘busy’ while the automation is executing, which may impact the user’s ability to work in parallel if the Bot execution is in the ‘foreground’ (i.e. opening applications, accessing user interface controls, etc.), however, the user can continue to work on the system if picture-in-picture feature is used.

 

 

Development Framework: Any Automation360 Development Framework can be used.

Solution Design (SDD): A sample SDD is linked here for your reference.

Administration: You’ll need a role defined that has an attended license assigned along with permissions to run the automation. One or more ‘custom roles’ could be created for this purpose - see samples at the following link.

Initiation: In this pattern, automation is initiated from the Automation Anywhere Control Room

Execution: Automations are executed on Local devices or on the virtual machines specifically assigned to the user in attended mode.

How to Use: Follow these steps to execute an automation.

  1. Log in to the Control Room.
  2. On the left pane in the public workspace, click Automation.
    A list of available automations is displayed.
  3. Select the automation to run. Hover over the actions menu (vertical ellipses) located to the right of the automation name and click Run Task Bot.


Kindly note that in this pattern, the automation ONLY consists of TaskBots. A Master/Main TaskBot is invoked, with/without SubBots. Forms are not used in this pattern.

Use cases where you can implement this solution pattern:

Staged Files Management
Imagine a scenario where a user needs to promptly organize and process a set of staged files. 'Run Local on Demand' enables swift execution within the user's environment, facilitating seamless management without undue delays.

Application Configurations
Setting up or configuring applications often involves intricate steps. This feature simplifies the process, allowing users to execute these tasks within their familiar environment.

Secure Logins and User Context Operations
Sensitive operations, such as managing secure logins or executing tasks within a specific user context, benefit immensely from the oversight and control this feature offers.

Troubleshooting Execution:

 

Problem Resolution

I don’t see AUTOMATION in the menu at all.

The user logging in to the Control Room to run the Bot needs a Role with ‘Run Bot’ access

I don’t see the folder containing the automation I want to execute

The user logging in to the Control Room to execute the automation needs a role with access to the folders containing Automations you need to be able to run/schedule.

Error “Either your username or your password is incorrect “

For the user representing the Bot Runner, the username/password in the “Device Login Credentials” section must be accurate.

 

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

 

 

Use cases where you can implement this solution pattern:

IT Support Ticket Resolution: In a large organization, IT support teams often receive numerous tickets for routine tasks such as password resets, software installations, or system updates. Using Automations with WLM, these tasks can be automated and executed remotely on-demand, reducing resolution times and freeing up IT staff for more complex issues.

Data Entry and Validation: Many businesses deal with large volumes of data entry tasks, such as updating customer records or processing invoices. By deploying Automations with WLM capabilities, these tasks can be performed remotely on-demand, ensuring data accuracy and improving operational efficiency.

Financial Reconciliation: Finance departments often need to reconcile transactions across multiple systems or databases. Automations can be utilized to automate the reconciliation process, and with WLM, these can be triggered remotely on-demand as needed based on the business needs, allowing finance teams to quickly identify discrepancies and ensure accurate financial reporting.
 

 

Run Remote via API with WLM

  • Using the Control Room API to add Work Items to a WLM Queue

 

 

Use cases where you can implement this solution pattern:

E-commerce Order Processing: E-commerce platforms often receive a high volume of orders that need to be processed efficiently. Automations can be triggered via API calls from the e-commerce system for each order to automatically process orders, update inventory levels, generate invoices, and send confirmation emails to customers.

Data Migration: When migrating data between different systems, Automations can handle data extraction, transformation, and loading (ETL) processes. Using APIs, Automations can fetch data from source systems, perform necessary transformations, and load it into the target system.

Healthcare Claims Processing: Healthcare organizations receive a large number of insurance claims that need to be processed. Automations can be invoked via APIs to automate tasks such as claim intake, validation, adjudication, and payment processing.
 

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

 

 

Use cases where you can implement this solution pattern:

Batch Data Processing: Many businesses need to process large volumes of data periodically, such as nightly batch jobs for data backup, data synchronization between systems, or data aggregation for reporting purposes. Automations can be scheduled to run remotely at predefined intervals via WLM to automate these tasks.

File and Folder Management: Businesses often need to manage files and folders on servers or cloud storage platforms, such as archiving old files, moving files between directories, or deleting temporary files. Automations can be scheduled to perform these file management tasks remotely at regular intervals.
 

 

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.

 
 

0 replies

Be the first to reply!

Reply