The order of assignments in Review harness
Hello,
When I spinoff three sub processes, four assignments are created. One from main process, and three from sub process, shown as below. My question is what order these assignments are sorted by.
For example, if I perform Step α of sub process 1 on top, next assignment, Step β is displayed between Step A of main process and Step 1 of sub process 3.
Initially I thought this is sorted by pxUpdateDateTime in ascending order, but it seems not really true. Why not bottom? Username of assignee has anything to do with this ("CW" comes before "D" because of alphabetical order)? I would like to know the exact logic. Also, how can I sort this in reverse (in descending order)?
Regards,
Accepted Solution
Updated: 26 Jul 2023 19:46 EDT
Pegasystems Inc.
JP
Worklist comes first, and workqueue comes second. Within each section, assignments are sorted by pxCreateDateTime in ascending order. Ascending order in time means the oldest ones come on top and the newest ones bottom. Username of assignee does not matter.
In your case, when you submit Step α of sub process 1, the assignment is deleted from Assign-Worklist table and next assignment for Step β gets newly created. The pxCreateDateTime of Step β is the newest among worklist assignments, so it will go to the very bottom of worklist section. I believe Step 1 of sub process 3 is a workqueue assignment, and that's why it still stays under Step β.
If you want to reverse the order from ascending order to descending order, override below Report Definitions and change the sort type of pxCreateDateTime from "Lowest to Highest" to "Highest to Lowest".
- Worklist - pyWorklistAssignmentsDefinition
Worklist comes first, and workqueue comes second. Within each section, assignments are sorted by pxCreateDateTime in ascending order. Ascending order in time means the oldest ones come on top and the newest ones bottom. Username of assignee does not matter.
In your case, when you submit Step α of sub process 1, the assignment is deleted from Assign-Worklist table and next assignment for Step β gets newly created. The pxCreateDateTime of Step β is the newest among worklist assignments, so it will go to the very bottom of worklist section. I believe Step 1 of sub process 3 is a workqueue assignment, and that's why it still stays under Step β.
If you want to reverse the order from ascending order to descending order, override below Report Definitions and change the sort type of pxCreateDateTime from "Lowest to Highest" to "Highest to Lowest".
- Worklist - pyWorklistAssignmentsDefinition
- Workqueue - pyWorkBasketAssignmentsDefinition
Thanks,
DXC
AU
@CloeW938 Can you share your flow diagram, you can trace the following when the flow is getting triggered you can see what activity are getting triggered to find.
Accepted Solution
Updated: 26 Jul 2023 19:46 EDT
Pegasystems Inc.
JP
Worklist comes first, and workqueue comes second. Within each section, assignments are sorted by pxCreateDateTime in ascending order. Ascending order in time means the oldest ones come on top and the newest ones bottom. Username of assignee does not matter.
In your case, when you submit Step α of sub process 1, the assignment is deleted from Assign-Worklist table and next assignment for Step β gets newly created. The pxCreateDateTime of Step β is the newest among worklist assignments, so it will go to the very bottom of worklist section. I believe Step 1 of sub process 3 is a workqueue assignment, and that's why it still stays under Step β.
If you want to reverse the order from ascending order to descending order, override below Report Definitions and change the sort type of pxCreateDateTime from "Lowest to Highest" to "Highest to Lowest".
- Worklist - pyWorklistAssignmentsDefinition
Worklist comes first, and workqueue comes second. Within each section, assignments are sorted by pxCreateDateTime in ascending order. Ascending order in time means the oldest ones come on top and the newest ones bottom. Username of assignee does not matter.
In your case, when you submit Step α of sub process 1, the assignment is deleted from Assign-Worklist table and next assignment for Step β gets newly created. The pxCreateDateTime of Step β is the newest among worklist assignments, so it will go to the very bottom of worklist section. I believe Step 1 of sub process 3 is a workqueue assignment, and that's why it still stays under Step β.
If you want to reverse the order from ascending order to descending order, override below Report Definitions and change the sort type of pxCreateDateTime from "Lowest to Highest" to "Highest to Lowest".
- Worklist - pyWorklistAssignmentsDefinition
- Workqueue - pyWorkBasketAssignmentsDefinition
Thanks,