Posted: 16 May 2018 7:14 EDT Last activity: 10 Aug 2018 6:05 EDT
pxAssignedUserName of Assign-Workliist not in sync with pyAssignedToOperator of pyWorkPage after GetNextWork
I use getNextWork button to pull the WO from a WorkBasket. The work is correctly getting assigned to user's worklist. But We have a section (from OOB RevisionManager) where WO(WorkObject) is listed and this section uses pyAssignedToOperator pyWorkPage property. As pxAssignedUserName and pyAssignedToOperator are not in sync , the UI section gives an impression that the WO(WorkObject) is still in WB(Workbasket) , despite it is moved to user's WL(WorkList).
Is this an expected situation ? Any help to fix this will be highly appreciated ?
Thanks for replying . I am using Revision Manager . Please see the attachment to see it . The section in question is called pyShowChangeSets which is OOB and it works on pyWorkPage of type RevisionManagement-Work-ChangeSet. It works correctly and displays the correct assigned to user on all other use cases of Revision Manager . I was expecting pyWorkPage(of type RevisionManagement-Work-ChangeSet) to reflect the newAssignPage (of Type Assign-Worklist). Are they supposed to be in sync ? Is this a bug with Pega ? Or is this an expected behaviour ? Could you please confirm.
My understanding was wrong here. There is no automatic syncing between said filds of pyWorkPage & newAssign Page . pyAssignedToOperator needs to be assigned a value manually in the code. So the question is conceptually incorrect.