PR_ASSIGN table is large for case type with stages defined
You notice that the PR_ASSIGN table contains entries for resolved work items with the flow pzinternalstageflow accumulating.
Steps to Reproduce
Create a case type with multiple stages, work the case to resolved status, then query the PR_ASSIGN table to see if there is a record for the case.
The root cause of this problem is a defect in Pegasystems’ code/rules. The logic doesn't currently check if the case is resolved prior to launching pzinternalstageflow.
Upgrade to PRPC 7.1.7.
0% found this useful