RWM Frequently Asked Questions
This content applies solely to Robotic Workforce Manager, which must be purchased separately from the Appian base platform. This content was written for Appian 21.4 and may not reflect the interfaces or functionality of other Appian versions.

Introduction

As you get set up and begin using the Robotic Workforce Manager (RWM) application, you might have questions or issues about the application. Check below to see if your question already has an answer!

General

Does RWM support one application in one environment integrating with multiple RPA vendors?

Yes, an RWM application can be connected to multiple RPA vendors. There are selection filters in the application to see objects in reports for one RPA vendor at a time versus all at once.

Does RWM support one application in one environment integrating with multiple servers of the same RPA vendor?

Yes, an RWM application can be connected to multiple servers of the same RPA vendor. There are selection filters in the application to see objects in reports for one server instance at a time versus all at once.

Why don't the robotic processes scheduled in RWM appear in the external RPA console's scheduler?

RWM retrieves scheduler data from the integrated RPA systems, but it does not push processes scheduled in RWM into external systems. RWM maintains its own scheduler system which kicks off those processes in the RPA system when the time comes.

No data are being pulled from the RPA system into RWM. What's wrong?

There may be a few things preventing RWM from retrieving data:

  • Is the ETL sync flag RWM_<RPA vendor initials>_FLAG_PROCESS turned on? The heartbeat process must also be on for versions prior to RWM 4.1.
  • Did the previous historic data load successfully?
  • Are there any data present in the RWM_WORK_ITEM_DETAILS table in RWM?
  • Were the end date and start date values set correctly? It's easy to accidentally set the end date to be after the start date. For non Blue Prism configurations, this is set in RWM_<RPA Vendor Initials>_HISTORIC_START_DATE and RWM_<RPA Vendor Initials>_HISTORIC_END_DATE. See similar question below for setting these values in Blue Prism.

RWM's resource statuses are not refreshing. What's wrong?

Is the ETL sync flag RWM_<RPA vendor initials>_FLAG_PROCESS turned on? The heartbeat process must also be on for versions prior to RWM 4.1.

Blue Prism

How do you increase the timeout for the WebService call from Blue Prism that pushes ETL data to RWM?

In Blue Prism, navigate to the System Tab > Web API Services > Appian Skill > Advanced Settings > and set the Timeout value.

How do you test Blue Prism and RWM connectivity?

In RWM 4.2 or newer, use the integration object in RWM RWM_testAppianWebAPICall to call a Blue Prism process that subsequently calls RWM. This tests both calls from RWM to Blue Prism and also for Blue Prism to call RWM.

When I run the ETL in Blue Prism to push data to RWM, I receive message 404 error “Unexpected error Error during Web API HTTP Request"

Check whether the checkbox value Expose is checked in the System tab > Web API Services > Appian Skill > Send Data to Appian > Parameters > Expose.

I'm running the historic load for RWM from Blue Prism, but no data are coming into RWM. What's wrong?**

Were all Blue Prism setup steps completed? And if so, were the end date and start date set correctly? It's easy to accidentally set the historic load end date after the start date. In Blue Prism, this is set within Blue Prism, in System > Processes / Objects > Environment Variables.

I'm using RWM 4.0.2, but the Blue Prism package won't import successfully.

Blue Prism 6.6 or newer is required for RWM 4.0.2 to be used with Blue Prism.

UiPath

Does RWM work with the community edition of UiPath?

No, UiPath Community Edition is not supported, only the UiPath Enterprise edition.

What is the difference between multi-tenant and multi-instance configurations of RWM with UiPath?

Multi-tenant refers to different tenants of the same UiPath Orchestrator, while multi-instance refers to using multiple, different UiPath Orchestrators.

Automation Anywhere

Integration calls from RWM to Automation Anywhere throws errors. If this is a result of special characters in the authentication credentials, such as a password or API key, how can I resolve this?

Escape the special characters such as underscores with a backslash \.

Open in Github Built: Wed, Aug 16, 2023 (04:37:39 PM)

On This Page

FEEDBACK