Issue

When the user updates urgency of the work object, existing assignments do not recalculate the urgency automatically.

Symptoms and impact

Assignment urgency does not change with the updates made to the urgency of work object.

Steps to reproduce

1. Create a work object and set a value to its pxUrgencyWork property.
2. Create an assignment for that work object. The pxUrgencyAssign value of the work object will be calculated at the time of assignment creation.
3. Update the pxUrgencyWork value on the work object and observe that the pxUrgencyAssign value of the assignment does not change correspondingly.

Root cause

This behavior is consistent with the current design of Pega code or rules.
The assignment automatically calculates the urgency only during the time of its initial creation.

Suggested approach

This issue is expected behavior for the current design of Pega code or rules.  An enhancement request has been entered for this issue but has not yet been assigned to a specific release.  This known Issue will be updated with release details when the enhancement for this issue is available.

In the meantime, perform the following steps to mitigate the issue:

1. Create a Declare OnChange rule.
2. Configure the Declare OnChange to run when the pxUrgencyWork property is changed.
3. Configure the Declare OnChange to call the OOTB resynchAssignmentUrgency activity from the Work- class to update the assignment urgency.

References

• Updating assignment urgency when work urgency changed
• Urgency
• Adjusting initial urgency for an assignment