Symptoms
When attempting to action a worklist item, the following error is experienced:
26030 Worklist item {SN} not found for {K2:DOMAINusername} at {IPAddress}
The task is still Active and the step is set with an Outcome = At Least 1 Person provides an approval.
Diagnoses
The Management worklist indicates that the task item is "Open" by another user, and the user attempting to action currently have the status "Allocated".
Resolution
Under some Destination Planning configurations:
- the number of slots generated
- how the user/group/role is resolved
- and how the boolean 'Alloc' parameter is called for OpenWorklistItem(SerialNumber, Platform,Alloc)
Will determine the worklist item's status (Available, Open, Allocated), when users are interacting with the worklist item. If a worklist item has one slot, but is assigned to two users, the following behavior will occur:
When a task is initially assigned, both user will see the task as:
John Smith - Available
Bob Marley - Available
Bob Marley was the first user to open the task form, but did not take an action and as such put the task into into the state below:
John Smith - Allocated
Bob Marley - Open
When John Smith tries to open this item from an email notification, the error "Worklist item could not be opened. 26031 All Worklist items {SN} Allocated for {K2:DOMAINusername} at {IPAddress}" is thrown. This is because when the task is "Open"-ed to Bob, only Bob Marley will be able to action the task unless one of the following action is taken:
1. The "Open" item belonging to Bob Marley is RedirectedDelegated to John
2. Bob Marley "Releases" the task, and put both item back into its "Available" state
One configuration to change this behavior can be used if applicable:
1. Run the Destination Rule configuration
2. Select back and the "Run this wizard in Advanced Mode" to enable Advanced Destination Planning
3. Use the "Plan per Destination" option and the "All at Once" option
4. On the next screen, use the "Create a slot for each destination." option and the "Resolve all roles and groups to users." option
5. Redeploy the process
When a new process instance is started next time, the same number of slots will be created for the number of users in the role (for the above case it would be 2) this way each users will have their only slot and as such will not run into the "Allocated" behavior.
Or if there is only one slot, OpenWorklistItem(SerialNumber, Platform,Alloc) with Alloc = false can be called such that the status does not change and will remain "Available".
