Posted: 30 Aug 2019 9:21 EDT Last activity: 3 Sep 2019 10:31 EDT
Unique constrain PR_ASSIGN_PK is violated for PR_ASSIGN table
I am currently facing an intermittent prod issue, which i am not able to replicate in lower environment. In this scenario user tries to submit a case, which has a pageList under pyWorkPage. On submission, system should create new work object for each page of that pagelist (say if there are 5 pages in that pagelist, then 5 new work object should be created) and the first case in which the pagelist exists would be resolved. However at times those new work objects are not being created but system resolves the first case. After adding some exception step we have come to know that, in this fail scenario unique constrain PR_ASSIGN_PK(associated with pzinskey) is violated for PR_ASSIGN table. And in this scenario obj save operation for PR_ASSIGN table is executed from Assign- Add_Assign activity.
I have gone through some article related to this type of issue, which mostly indicated about background agent processing or creating temporary cases on the same page where the new work objects are created or External user's parallel action. However these theories are applicable in my scenario.
***Edited by Moderator Marissa to update platform capability tags****
The new cases in question here are not following typical parent child relation here. We are not using pzCreateCase here. Basically we are looping through the page list and inside the loop we are calling an custom activity. Inside this activity we are getting stage ID , creating workpage and then AddCoveredWork has been called on that same step page.