This setup guide is intended for customers using Appian 20.1 or later and Blue Prism versions 6.4, 6.5, and 6.6.
The zip file has the following Appian components:
Appian Application Package Setup requires four steps:
Run the SQL Scripts with Tables, Views, Function, and Procedure queries as described below:
Use the Cloud Database site (shown below).
Click Import (shown below) on the top right and upload the files one by one in the order below, clicking Go to run each script.
Self-managed customers or in-house database users can execute the SQL scripts one by one.
Next, import the MySQL scripts in the order below. You can find the scripts in the folder Scripts.
You can find the list of plugins in the Prerequisites document. To add the plugins:
When logging into Appian as an Administrator, a screen similar to the below image will open. Open the menu and click Admin Console.
Click Plug-ins in the left-hand menu of the Admin Console.
Click Deploy New Plug-ins and a pop-up window with a search bar appears.
Search for the given plug-ins, click on them, and deploy each plug-in.
To successfully import an application package, the service account user who deploys the application package must be in the GMT time zone and must not be changed.
Click on the menu and navigate to the Appian Designer.
Upload the Robotic Workforce Manager<\version>.zip file to the Package (ZIP) section. Make changes to the Robotic Workforce Manager.properties as mentioned below.
Note: If your installation of RWM only requires Blue Prism set up, don't modify the RWM_UI_PATH_CSP and RWM_AppianRPA sections in the properties file.
Robotic Workforce Manager.properties
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Provide the Appian environment URL ex:https://xyz.appiancloud.com ## Constant: RWM_VAL_APPIAN_DOMAIN_NAME ## Type: Text ## ## Text values will be displayed in Appian exactly as they are ## specified here. No spaces are trimmed. Values do not need to be ## encased in quotation marks. content._a-0000e23d-7780-8000-9ba2-011c48011c48_64089.VALUE= [http(s)]://[Appian URL] Appian business database name ex:jdbc/Appian ## Constant: RWM_VAL_COMMON_DATA_STORE_APPIAN ## Type: Text ## ## Text values will be displayed in Appian exactly as they are ## specified here. No spaces are trimmed. Values do not need to be ## encased in quotation marks. content._a-0000e23d-7780-8000-9ba2-011c48011c48_69762.VALUE=jdbc/[Database Name] The following are UiPath specific connected system, no modifications are needed these details are configured directly from the database in below steps ## Connected System: RWM_UIPath_CSP connectedSystem._a-0000e2f2-a540-8000-e99f-01ef9001ef90_314069.host=http(s)://<UIPath_Orchestrator_URL> connectedSystem._a-0000e2f2-a540-8000-e99f-01ef9001ef90_314069.port=<Port_Number to access UIPath Orchestrator> connectedSystem._a-0000e2f2-a540-8000-e99f-01ef9001ef90_314069.tenant=<Host_Name to access UIPath Orchestrator> connectedSystem._a-0000e2f2-a540-8000-e99f-01ef9001ef90_314069.userName=<Username to access UIPath Orchestrator> connectedSystem._a-0000e2f2-a540-8000-e99f-01ef9001ef90_314069.password=<password> The following are Appian RPA http connected system, for API Key Value, use "Bearer <apiKeyValue>" This API Key must be related to a service account in Admin Console. The service account should have an System Administrator access. ## Connected System: RWM_AppianRPA connectedSystem._a-0000e3be-674f-8000-9ba5-011c48011c48_30431.baseUrl=[http(s)]://[Appian URL]/rpa/ connectedSystem._a-0000e3be-674f-8000-9ba5-011c48011c48_30431.apiKeyValue=Bearer <apiKeyValue>
Click the Include related import customization file checkbox and upload it to the Import Customization File (PROPERTIES) section.
Click Inspect. If the inspection returns without any warnings or conflicts, then you are ready to move on to the next step of importing. If you're shown unexpected warnings or conflicts, please contact the support team.
Click Import. Due to the size of this application, it may take a while to import, at which point the screen may time out. This is expected, and the import is still occurring in the background.
To configure the vendor details, you need to be a member of the RWM_Admin group.
Click Add New Environment and enter the details.
To add the instance details:
On this tab, click Add New Instance to add all the instance details in accordance with vendor details. Disabled fields are not required.
The Robotic Workforce Manager package consists of the Robotic Workforce Manager<\version> -> BP Release Robotic Workforce Manager.bprelease file, which contains multiple objects to be setup in the Blue Prism Environment.
One dedicated run time resource is needed to manage the RWM application.
These objects are required to be added to the Blue Prism environment:
To add the objects:
Log into Blue Prism, click on File > Import.
To enable SQL server authentication:
Right-click on the server and go to properties as in Figure 18.104.22.168 (c).
In properties, check SQL Server and Windows Authentication mode and click OK as shown in Figure 22.214.171.124 (d).
Pre-setup steps You'll need to set up Appian skill and credentials before importing the ".bprelease" file.
This includes configuring:
For RWM Blue Prism server and Appian credentials, provide the following access rights:
Refer to Figure 126.96.36.199.1.2.2 (a) for the location of the credentials.
Exposing business objects
Expose the following objects:
To communicate from Appian to Blue Prism:
In Bue Prism, go to System > Objects > Exposure > Expose a Business Object as shown below.
Enter the full name of the objects listed above. This includes the exposed object name and the object name indicated within the parenthesis (for example
RWM Add to Queue (RWMAddtoQueue)). None of the checkboxes need to be selected as shown below.
To set up RWM ETL Scheduler:
To set up RWM Schedules:
Data are loaded from Blue Prism to Appian on a daily basis by running the ETL process on the Blue Prism side. The process could also be used to load historic data into Appian.
To load the historic data, the environment variables below should be configured:
Once the above values are configured the process RWM_getDataFromBPToAppian needs to be started manually.
A scheduled ETL process runs every day (configured for 1 A.M. GMT nightly) to collect Blue Prism statistics and move them to Appian via a predefined web service. The timing of this run is configurable. Users can configure the timing by navigating to the scheduler called RWM ETL Scheduler in Blue Prism. After which the RWM ETL task needs to be selected and the process RWM_getDataFromBPToAppian needs to be added against either a particular resource or to a pool.
Once the data is loaded into Appian, the dashboards carry the last updated timestamp on each screen (top right corner).
It should be noted that the application can only show data as of the previous schedule (typically the previous day, alternatively known as T-1 data). The application only supports the near real-time data collection only for the Processes Started & Scheduled from Appian, Resource Alerts, and for fetching exceptions into Appian.
Data regarding Process, Queue, Work Items, Resource information, and other metrics are transported from Blue Prism to Appian on a daily basis. A scheduler invokes a Blue Prism robot to execute a process, which runs several queries. The response is converted to a JSON and moved to Appian via the endpoints configured on Appian's side.
Once a user starts or schedules a process, the process name, its input parameters, scheduled time (aka deferred time, if scheduled) and Appian-generated reference ID are sent to Blue Prism via Appian Web API. In Blue Prism, an object called HIL Populate Queue will be invoked (in Background mode), which creates a work item based on this information. These processes will be triggered passively in Blue Prism via a Blue Prism Scheduler.
Currently, we support the close to real-time (five-minute delay) extraction of the Process (Start/Schedule execution) and Resource Status from Blue Prism. For this, there are two processes in Appian that are scheduled to run for every five minutes. The processes pass a query to extract the process/resource status frequently to an exposed Blue Prism object, which runs the query and provides the response to Appian. This response will be updated in Appian.
Currently, the exception management reference app has been developed in Appian and Blue Prism, where Appian is used as a tool to manage the exceptions raised from Blue Prism. This module automatically pulls exception work items from Blue Prism and sends them to Appian, where they will be assigned to a specific user or group based on the routing logic at Appian. If a match in the routing module is not found, the exceptions will be sent to the Exception Manager for assignment.
On This Page