Work object stale assignment issue - Related existing article - SA-7300
Hi,
As per the mentioned article - caseStale assignment issue is fixed in PRPC 6.3. I am working in verison 7.1.8 and issue exist in the system.
RULE-OBJ-ACTIVITY WORK- REASSIGN
Kindly request support for the issue.
Thank You!
Jayami
URL to SA-7300: https://pdn.pega.com/support-articles/work-object-stale-assignment-issue
***Updated by moderator: Lochan to add Categories; edit text***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
BlueRose Technologies
AU
Hi,
So, you have implemented the solution given in the article for 7.1.8 version and issue still persists. Is my understanding right?
EvonSys (Pvt) Ltd
SG
Hi Prudhvi,
I havent implemented that because we are not able to reproduce the issue in Development environment yet. But issue exist in Production and UAT environments. Still couldnt find the root cause of the issue.
Regards,
Jayami
BlueRose Technologies
AU
Hi Jayami,
In the SA-7300, the root cause is given as "The out-of-the-box activity 'Reassign' does not handle Page level error messages."
Does it differ in your scenario.
EvonSys (Pvt) Ltd
SG
Hi Prudhvi,
There are few work objects in User's work list which are "Resolved Completed". When I open the case it diaplays below error message.
"Assignment Error - Work Item's assignment has been changed"
Any idea how to fix the issue?
Thank you!
Jayami
Techmahindra
IN
Hi Sivatejai,
The usecase referred on top was a different one where User is using Obj-Save method with writenow parameter in the activity called through utility shape and the error is thrown. Hence the suggested approach was to deselect the writenow parameter used with Obj-save method.
I am assuming your usecase to also be a different one probably a SR might be required to further look into it.
Regards,
Shanthini Charles
Pegasystems Inc.
IN
Hi Meena,
I looked into the SR for you and here's what I found in the Resolution: Issue was because of using the Writenow parameter with Obj-Save. It was resolved after deselecting the writenow parameter used with Obj-save method.
Hope this helps!
Regards,
Ford
IN
Thanks Lochana For your response.
Could you please let me know the rule where the change has been made? Is it any OOTB rule or their Application specific rule.
In our application we haven't used Obj-Save with Write Now Param but still facing issue.
Thanks,
Meena S
Pegasystems Inc.
IN
Hi Meena,
The WriteNow parameter is an OOTB one designed for a specific purpose. It was used incorrectly in the above case. Here are the related articles, but you could find more by searching on PDN.
When to set the WriteNow parameter in the Obj-Sav and Obj-Delete methods
What exactly is the error you are facing? The above SR was for this error message: Error: Flow Not At Task
If you are unable to find more information on PDN to resolve this, I'd recommend that you create a new post for a focussed troubleshooting. To do that, click Write a Post button on the right pane above!
Regards,