Human In-The-Loop means that user involvement is expected during the automation's invocation - and possibly during its execution. Click the link below matching the Solution Pattern Model for your use case for additional details and assets for each Solution Pattern. How will your automation be executed?
Desktop Automation
There are 4 Solution Patterns for running Desktop Automation. These Solution Patterns are generally executed locally on the user’s machine/desktop (optionally including ‘Picture in Picture’ mode) and use a Process to join together Task Bots and human-readable forms.
Co-Pilot Desktop - Standalone - Run on Demand
- User invokes automation when required, via Control Room, or Copilot Desktop Assistant.
- Stand alone’ = not embedded in any application (no application/screen/transactional context)
- Can be used with “Picture in Picture”
- Automation renders in a ‘picture in picture’ screen (using Microsoft’s Child Sessions built into Windows), allowing the user to continue to use their machine, also allowing interaction with forms in the PIP window when necessary
-
- Example: Call center scenarios, where an agent needs to execute automation (ex. Servicing a caller request such as unlocking a cell phone), while still using their machine for other tasks (ex. Email, etc)
Co-Pilot Desktop - Standalone - Run via Event Trigger
- Automation is invoked when a triggering event occurs (ex. File/folder updated, email received, hotkey, etc)
- Can be used with “Picture in Picture”
- Automation renders in a ‘picture in picture’ screen (using Microsoft’s Child Sessions built into Windows), allowing the user to continue to use their machine, also allowing interaction with forms in the PIP window when necessary
-
- Example:
- Staff launches an automation via hotkey, and received healthcare invoices are processed.
- Document Automation extracts data from documents and enters extracted data into a system of record
- Users validate form data and validate handwriting from medical staff/physicians, after which business systems are updated.
Co-Pilot Desktop - Embedded in a Business App - Run on Demand
- Automation capabilities are embedded into Enterprise Applications (Ex. Salesforce, Genesys) or other web-based business application (Ex. Service Now, Workday).
- These capabilities can be by means of custom iFrames or through the use of Automation Co-Pilot Extensions for any web based application that is accessed through Google Chrome.
- Automations embeds are ‘context aware’ - meaning they can be made available in specific systems, on specific screens, so they can access/read information on the screen to use as input for the automation.
Co-Pilot Desktop - Embedded in a Collaborative App - Run on Demand
- Automation capabilities are embedded into Collaborative business applications (currently Microsoft Teams)
- Users can easily access automations without leaving the application
- Automations are not ‘context aware’ - meaning they can run with a simple form for input as the automation wouldn’t be able to read other content from the collaborative app.
Process Automation
There are 3 Solution Patterns for running Process Automation. These Solution Patterns involve an invocation of a Co-Pilot process - which orchestrates automation tasks, with human tasks by way of custom forms. These automations execute on Device Pools, and have no requirement for a local installation of the Bot Agent.
Co-Pilot Process - Stand Alone - Run on Demand
- User invokes automation when required, via Control Room, or Copilot Desktop Assistant.
- Stand alone’ = not embedded in any application (no application/screen/transactional context)
- Automations execute on a Device Pool (headless/unattended)
- Perfect for scenarios where the automation doesn’t require specific application context, and a human initiates the process
- Example: A business user may need to initiate a customer/supplier/partner onboarding process involving human input (forms) and automation across several applications.
Co-Pilot Process - Embedded in Business App - Run on Demand
- User invokes automation when required via Widget in the business application powered by Co-Pilot.
- These capabilities can be by means of custom iFrames or through the use of Automation Co-Pilot Extensions for any web based application that is accessed through Google Chrome.
- Automations embeds are ‘context aware’ - meaning they can be made available in specific systems, on specific screens, so they can access/read information on the screen to use as input for the automation.
- Example:
- Processes related to an “Opportunity” on a specific Salesforce Screen (order validation involving Salesforce data + lookups, contract documents, etc)
Co-Pilot Process - Embedded in a Collaborative App - Run on Demand
- Automation capabilities are embedded into Collaborative business applications (currently Microsoft Teams)
- Users can easily access automations without leaving the application
- Automations are not ‘context aware’ - meaning they can run with a simple form for input as the automation wouldn’t be able to read other content from the collaborative app.
- Automations execute on a Device Pool (unattended); No local Bot Agent installation is required
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.