Modify Historical Load

Introduction

Robotic Workforce Manager (RWM) includes an extract, transform, load (ETL) process that loads data from Appian RPA based on a configurable time interval.

This page describes the ETL historic load process and best practices to keep in mind when configuring the historic load for Appian RPA, Automation Anywhere, UiPath, and Blue Prism.

Learn more about the RWM background processes that keep your data up to date in the application.

What is a historical load?

When the RWM app is deployed, it needs to populate data from the RPA server. This is known as the historical load. Users can bring up to 12 months of data, but this number can be decided based on their company policy.

Configure historical load

RWM uses a process model to populate the initial or historical load:

• For Appian RPA users, this is the RWM JD ETL Wrapper Model Process.
• For Automation Anywhere users, this is the RWM AA ETL Wrapper Model Process. It also takes the following details from Automation Anywhere any time the ETL runs (every 15 minutes by default):
  • Bots
  • Executions
  • Resources
  • Queue
  • Queue Items
  • Scheduled Details
  • Work Item
• For UiPath users, this is the RWM UI ETL Wrapper Model Process. It also takes the following details from UiPath any time the ETL runs (every 15 minutes by default):
  • Robots
  • Jobs
  • Session
  • Process
  • Queue
  • Queue Items
  • Scheduled Details
  • Release
  • Work Item

To configure the historic load:

1. Open the RWM_<vendor>_HISTORIC_LOAD_FLAG object.
2. Modify the load flag constant to be true. If it is not true, the historic load process will not run.
3. Open the RWM_<vendor>_HISTORIC_START_DATE and RWM_<vendor>_HISTORIC_END_DATE objects.
4. Modify the start date and end date constants to specify the time period. We recommend that customers load at least 3 months of data for dashboards to be meaningful.
5. Run the RWM <vendor> ETL Wrapper Model Process, process.
6. When the process is complete, open the RWM_<vendor>_HISTORIC_LOAD_FLAG object once more.
7. Modify the load flag constant to be false after running the historic load. This will ensure that the historic load is turned off and does not interfere with the daily ETL load.

The historic load process is resource-intensive and may impact performance. We recommend that users not run the historic load more than once daily or during business hours.

Blue Prism

The process RWM ETL Scheduler Process is used to populate the initial or the historic load.

To configure the historic load:

1. Open the RWM HistoricUpdate environmental variable.
2. Modify it to true. If it is not true, the historic load process will not run.
3. Open the RWM HistoricQuery StartDate and RWM HistoricQuery EndDate environmental variables.
4. Modify the start date and end date to specify the time period. We recommend that customers load at least 3 months of data for dashboards to be meaningful.
5. Run the RWM ETL Scheduler Process process.
6. When the process is complete, open the RWM HistoricUpdate Flag environmental variable once more.
7. Modify it to be false after running the historic load. This will ensure that the historic load is turned off and does not interfere with the daily ETL load.

The historic load process is resource-intensive and may impact performance. We recommend that users not run the historic load more than once daily or during business hours.

Login agent

The login agent is a Windows service installed on every runtime resource. Its main functionality is to lock the resource when not in use and unlock it when it should be running a process. Blue Prism has provided an object with the following functionality:

• Login
• Logout
• Is Locked
• Is Locked In

Feedback