Appian RPA Configurations

Configuration of Daily ETL Process

The RWM Application shows data from the Appian database. However, the data itself comes from the Appian RPA Server. In order to extract key Appian RPA data such as Processes, Resources, Queues, and Work Items in Appian tables, the Appian process - the RWM JD 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

This process - RWM JD ETL Wrapper Model 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_JD_HISTORIC_LOAD_FLAG should be enabled.
  • To give the duration RWM_JD_HISTORIC_START_DATE and RWM_JD_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 variable - RWM_JD_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_JD_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.

't

  • Do not run the historic load more than once daily.
Open in Github Built: Fri, Mar 11, 2022 (04:59:07 PM)

On This Page

FEEDBACK