What is the diff between work object key and assignment key?
can same assignment be assigned to different work queues?
is there a restriction to number of assignments assigned to a user?
Work object key is the case id key and which is constant for a particular case during end to end processing. It will be in the format of “class caseID”. Will find this value in pyWorkPage.pzInsKey in the clipboard in a case thread.
Assignment key is different and it holds key for specific flow in the case . The key format will be "ASSIGN-WORKLIST class caseID!Flowname . This property will be present in newAssignmentPage.pzInsKey in the clipboard when the case is in perform mode.There is no specific restrictions on assignments transfer to a user.
Work object key is the primary key of the work table to uniquely identify a work object.
Eg: pzInsKey for the work table in Pega
Sample value of pzInsKey = ORG-APPNAME-WORK D-1
One workobject can have multiple assignments at a time.
Assignments are stored as instances of Assign- classes like Assign-WorkList, Assign-WorkBasket
The reference to an assignment is stored inside the work object in .pxFlow(FlowName).pxAssignmentKey
Sample value of pxAssignmentKey (if the assignment is assigned to a workbasket) = ASSIGN-WORKBASKET ORG-APPNAME-WORK D-1!WBNAME
If we see the ASSIGN-WORKBASKET instances, we find an entry whose pzInsKey will be ASSIGN-WORKBASKET ORG-APPNAME-WORK D-1!WBNAME (pxAssignmentKey as stored in .pxFlow(FlowName) page group)
- Work Object Key - pzInsKey of the WorkObject or the Case
Assigment Key - pzIsnkey of the Assignment in the Assign-Worklist or Assign-Workbasket
-
Yes, it’s possible to reroute the assignment to different work queues.
-
No restrictions. Too many open assignments in their worklist would confuse users when it comes to prioritizing their work.