Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Devendra Pawar (Pawar)
Siemens

Siemens
Pawar Member since 2022 29 posts
Siemens
Posted: Oct 23, 2018
Last activity: Nov 20, 2018
Posted: 23 Oct 2018 2:21 EDT
Last activity: 20 Nov 2018 13:42 EST
Closed
Solved

Stale Assignment Created

Hi,

When user completed current assignment and route case to next flow then next flow unable to create.so assignment key is missing for next assignment.so assignment still remain in current user work list with stale assignment creation which is already submitted by this user .Please refer the attached screenshot for the same and please provide you comments for this issue.it will be helpful for me. Thanks in advance

***Moderator Edit-Vidyaranjan: Updated SR details***

To see attachments, please log in.
Dev/Designer Studio
Case Management
Support Case Exists

Accepted Solution

Posted: 6 years ago
Posted: 23 Oct 2018 8:06 EDT
Carissa Wenhardt (CarissaW_GCS)
PEGA
Senior Principal Engineer, Technical Support, Industry Apps
Pegasystems Inc.
US

If there was an error in the flow processing then I would expect the transactions to roll back. If there are places where a Commit or Obj-Save with write now is used, then it could cause issues where not all of the data is rolled back as expected. If you are able to reproduce the issue, you can collect a trace to see where it is going wrong. If you are unable to reproduce the issue then I suggest reviewing the rules executed in the working scenario and checking for any commits or immediate Obj-Save steps.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice