Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Assignment SLA does not work for ScreenFlow



SLA does not work for the  ScreenFlow. The Initial Urgency is added twice when the Goal time is reached.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Flow rule which has a sub-process shape followed by assignments.
  2. Create a screen flow.
  3. Invoke the screen flow from the main flow.
  4. Set the SLA at the flow level and the work object level.
  5. Execute the test case.

Root Cause

When the Goal time is reached, the initial Urgency is added multiple times to the work object Urgency. In the ExecuteSLA activity, the pxUrgencyWork is calculated at Step13,

pxUrgencyWork - Calculated as pxUrgencyWorkClass+pxUrgencyWorkSLA+pxUrgencyWorkStepSLA

pxUrgencyWorkClass - Default value is 10

pxUrgencyWorkSLA - Calculated as sla.pyUrgencySLA(initial urgency in SLA) + sla.pyEscalations(Goal).pyEscalationUrgency (Goal time Urgency increase count)

pxUrgencyWorkStepSLA - Initial urgency when this step reached. This already contains the initial urgency of the SLA rule. Hence, the initial urgency is added twice.


Perform the following local change:
  1. Avoid using the Initial Urgency for the flow.
  2. Declare Expression - pxUrgencyWork is an Available rule and can override the pxUrgencyWork declare expression rule to build an expression which is suitable according to the requirement. Removing the pxUrgencyWorkStepSLA from the expression must provide a result that is similar to the working of the stage SLA.

An enhancement request, FDBK-64151, is created for consideration by Pega Product Management.

Suggest Edit

Published January 2, 2020 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us