UI Path Configurations


Robotic Workforce Manager (RWM) includes an extract, transform, load (ETL) process that loads data from UiPath every night. This process can be configured if needed.

This page describes the ETL historic load process and best practices to keep in mind when configuring the historic load.

Configuration of Daily ETL Process

The RWM Application shows data from the Appian database. However, the data itself comes from the UiPath Server. In order to extract key UiPath data such as Processes, Resources, Queues, and Work Items in Appian tables, the Appian process - the RWM UI ETL Wrapper Model Process is scheduled to run every day.

By default, the process is expected to run at 1 A.M. daily. It should be noted that the time mentioned here is as per the timezone of the Appian Server, which by default uses GMT. Thus, unless specific changes are made, the ETL jobs are expected to run at 1 A.M. GMT.

Configuring Historic Data Load

The RWM UI ETL Wrapper Model Process will take the following details from UiPath every day at 1 A.M.:

  • Robots
  • Jobs
  • Session
  • Process
  • Queue
  • Queue Items
  • Scheduled Details
  • Release
  • Work Item

This process is also used to populate the initial or the historic load. The idea behind the historic load is that when the RWM app is deployed, we need to bring in data from the Appian Server. Users can bring up to 12 months of data, but this number can be decided based on their company policy.

To configure the historic load:

  • RWM_UI_HISTORIC_LOAD_FLAG should be enabled.
  • To give the duration RWM_UI_HISTORIC_START_DATE and RWM_UI_HISTORIC_END_DATE should be given.
    • It is advised that customers bring in at least 3 months of data for dashboards to be meaningful.

  • Change the environment variable - RWM_UI_HISTORIC_LOAD_FLAG Flag to true before running it for the historic load.
    • If it is not true, the historic load process will not run.
  • Change the environment variable - RWM_UI_HISTORIC_LOAD_FLAG Flag to 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.

Do not run the historic load more than once daily. Do not run during business hours since this process use more resources.

Open in Github Built: Fri, Mar 11, 2022 (04:59:07 PM)

On This Page