Configure processes in Process Composer

Automation Co-Pilot provides front-office and back-office automations, where the Bot Creator user creates a process workflow with human and bot tasks as per the business requirement.

A Bot Creator user can configure a process in the Process Composer in the Control Room. The Process Composer provides a drag-and-drop interface to help create process flows. It enables the user to configure when a bot should be executed. It also displays correct data to the users and exchanges the data across multiple teams.

Designing processes

A process consists of human and bot tasks. A process contains the following components:

An entry form which is the first step in a process.
A sequence of process elements as follows:
- Forms or Task Bots
- Input, output, and meta-variables to share data
Logical conditions such as If, Else for internal and conditional branching of the process.
End states to close each request such as completed, failed, or canceled.

The image describes the components of an AARI process

Designing forms

A Bot Creator user can create a form and enter the required data by using form elements that can be rendered in the web interface. They can add or remove form actions when creating processes.

As a user, you can interact with the form only when it is assigned to you. If the form is unassigned, it is not enabled and is read-only. To edit the form, you can assign the form either to yourself or to any member of the team who has access to the process. After editing the form, the assignee can either submit the form or use any other action options. After the form is submitted or an action option is used, the request view displays the next step or task.

In the web interface, the following elements are supported in a form:

Checkbox
Date
Document
Dropdown
Hyperlink
Image
Label
Number
Password
Radio Button
Rich Text Editor
Select File
Table
Text Area
Text Box
Time

Designing Task Bots

A Bot Creator user can create a Task Bot that will execute inside the process by using the input and output variables. When the Use as input check box is selected, the process passes data into the input variables, and when the Use as output check box is selected, the process gets data from the output variables after bot execution.

Process workflow

The following workflow describes the steps involved in building a process and making it available in the web interface:

Other tasks

Depending on the requirement, a Bot Creator user can also perform other tasks after creating a process:

If there is a change in the requirement, a Bot Creator user can check out the process to their private workspace and edit the process according to the requirement.
Check out a process.
The Bot Creator can test the process before checking it in by running it in the private workspace.
You can run the process either in the public or the private workspace using the Run option in the Process Composer . The bots in the private process executes on the default device of the Bot Creator.

When the private process is executed, the Bot Creator can create a request, enter data in the initial form, and run their request from the private workspace. Requests created from the private process execution can be viewed only by the user creating the request. Requests created from the public process execution can be viewed by the AARI Admin. Managers and users can view the requests only if they have access to the process.

Run a process.
Access a process from one Control Room to another by either importing or exporting the process. For example, if a process is developed and tested in the staging pod and is now ready for production, it can be exported from the staging pod. Similarly, this exported process can be imported into the production pod.
- Import a process.
- Export a process.
If a requirement becomes redundant, the created process can be deleted.
Delete a process.

Automation 360