Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

How Pega Robot Runtime and Pega Workforce Intelligence work together

Updated on November 5, 2019

The following summary describes how Pega Robot Runtime works with Pega Workforce Intelligence after everything is configured and enabled.

  1. Pega Robot Runtime starts. Typically, it is set up to start when Windows starts.
  2. Pega Robot Runtime connects to Pega Workforce Intelligence and determines if the expected work hours have been received for the day.
    If this information has not been received, in the Enter the Expected Work Hours window, the associate is prompted to enter the hours that they expect to work.
  3. Pega Robot Runtime collects information based on the associate’s activities and sends this information to the Pega Workforce Intelligence server.
  4. After an idle period that exceeds the amount of time specified in the secondsForIdle key, Pega Robot Runtime connects to Pega Workforce Intelligence and retrieves the Off Computer Time Reason codes.
  5. Pega Robot Runtime presents these reason codes to the associate on the Select Reason for Inactivity window.
    • If the associate canceled the Enter the Expected Work Hours window when prompted at the beginning of their shift, or if Pega Robot Runtime was never shut down from the previous shift, the associate is again shown the Enter Expected Hours window and is prompted to enter that information.
    • If the associate clicks Cancel on the Select Reason for Inactivity window, the time is marked as idle.
  6. Pega Workforce Intelligence analyzes and then presents the information that is captured by Pega Robot Runtime to the Pega Workforce Intelligence user.

Tags

Pega Workforce Intelligence System/Cloud Ops Administrator

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us