Question
Randstad Technologies US
US
Last activity: 14 Nov 2017 12:16 EST
Get next work successindicator -23 error
Some specific users are getting no assignments found when clicking next assignment.But for others who has same profile..its working fine.
In the logs we are able to see successindication values as -23.( // work object points to different assignment)
How we can fix it.
Thanks in advance.
Pegasystems Inc.
US
Each assignment has a pxRefObjectKey that points to a case, plus has a flow name property.
Cases have a pxFlow() page group where each page has a pxAssignmentKey property.
.pxFlow( <flow name> ).pxAssignmentKey value should match the pzInsKey of the assignment.
If not, the the case and assignment are out-of-sync.
This can be caused by issuing commits outside the FinishAssignment activity.
Randstad Technologies US
US
Thank you Pedel for the response. Please let me understand in which scenarios we will get success indicator -28. What could be possible reasons for that?
Pegasystems Inc.
US
See java step 10 of Assign- acquireWorkObject
Pegasystems Inc.
US
Was a flow changed, removing an assignment, while cases were active?
FYI: The 7.3 LSA course has a lesson titled "Handling flow changes for cases in flight" in 12. Post Production Events.
////////////////
java step 7 within Work- OpenAndLockWork
Pegasystems Inc.
US
Was a flow rule updated in such a way that an existing assignment was removed - an assignment at which cases are currently active?
There are 3 ways to deal with this situation:
1) Brute force (not recommended); define a different application, force users to switch back and forth
2) Batch process every case affected by the flow change moving them to a valid assignment. The drawback to this is approach is potential performance impact plus having to take into consideration that the case might be open.
3) Leave the existing assignment in place but disconnect its input connector(s). After all existing cases have moved beyond that assignment, remove it from the flow.
Circumstancing a flow is possible but is overly complex to manage so is also not recommended.
Randstad Technologies US
US
Pedel we are facing quite a few issues in getnext work in production.
we customized getnextwork in such a way, on every assignment a flow will be called.in that flow it may resolve the entire case based on some conditons.
1)if case is revoved,system will go for next assignment
2)if data conditioning is fasle,system will bick that assignment for processing.
As flow is executingon every assignment ,its taking more time to find correct candidate due to which users are faicng latency issues.
and due to this latency ,when other user try to get assignemtn,we are observing many locking related issues.
Could you suggeste best approach to reduce the latency and avoid the locking issues.
Thanks for your help.
Pegasystems Inc.
US
Hard to picture what you are doing. Starting a flow during GetNextWork?
The other arround, you can have GetNextWork automatically invoked during flow processing when not able to reach the next assignment due to security restrictions or the case is resolved. You configure that on the flow rule.
If a case resolves you want it to remove all of its assignments - pxForceCaseClose will do this.
Sounds like you have a complex "skill matching" requirement for Get Next Work. Is that the crux of the issue are experiencing?
No idea why anyone would want to spin off a flow in the process of retrieving work.