The RWM application was deprecated with Appian 24.1. The application will no longer be updated or pre-installed for new Appian Cloud sites with Appian RPA enabled. RWM will be removed in a future release and we encourage customers to use the Operations Console to manage robots instead. |
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.
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.
RWM uses a process model to populate the initial or historical load:
RWM JD ETL Wrapper Model Process
.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):
RWM UI ETL Wrapper Model Process
. It also takes the following details from UiPath any time the ETL runs (every 15 minutes by default):
Tip: RWM objects are named to reflect your chosen RPA vendor. In the following instructions, replace <vendor>
with:
JD
for Appian RPAAA
for Automation AnywhereUI
for UiPathTo configure the historic load:
RWM_<vendor>_HISTORIC_LOAD_FLAG
object.true
. If it is not true
, the historic load process will not run.RWM_<vendor>_HISTORIC_START_DATE
and RWM_<vendor>_HISTORIC_END_DATE
objects.RWM <vendor> ETL Wrapper Model Process
, process.RWM_<vendor>_HISTORIC_LOAD_FLAG
object once more.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.
The process RWM ETL Scheduler Process
is used to populate the initial or the historic load.
To configure the historic load:
RWM HistoricUpdate
environmental variable.true
. If it is not true
, the historic load process will not run.RWM HistoricQuery StartDate
and RWM HistoricQuery EndDate
environmental variables.RWM ETL Scheduler Process
process.RWM HistoricUpdate Flag
environmental variable once more.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.
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:
Modify Historical Load