Summary

The RequiredSkills Declare Index is not executed when an assignment is routed to workbasket. Hence, there is no match while using GetNextWork.

Error Messages

Not Applicable

Steps to Reproduce

1. Configure a flow process with a Worklist Assignment shape
2. Use a custom router to specify the skills and set param.SwitchToWorkbasket to True for cases that should be routed to a workbasket instead of the worklist
3. Run the process to create the assignment

Root Cause

An issue in the custom application code or rules where AddAssign is started with a class of Assign-Worklist and then switched to Assign-Workbasket. The RequiredSkills Declare Index does not fire in this scenario since the Declare Index is defined on Assign-Workbasket. However, the properties are added when the page scope is Assign-Worklist.

The change tracking occurs with pxSubscript and pxSkillsRequired properties defined on the RequiredSkills Declare Index. The Page class is Assign-Worklist when the properties are added. Hence, they are not tracked as the Declare Trigger is for Assign-Workbasket. The properties should be tracked if they are added after the change in Page class.

Resolution

Perform either of the following local-changes:

1. Modify the flow to contain both a worklist and a workbasket assignment
2. Use a Decision shape to route to the appropriate assignment shape based on the business logic

or

Modify the Assign- AddAssign activity which is available to include custom logic. The Declare Index executes if the skills are set within it. This occurs since the page class is set to Assign-Workbasket.