Question

4
Replies
261
Views
YEUNA Member since 2007 5 posts
PEGA
Posted: 3 years ago
Last activity: 3 years 1 month ago
Closed
Solved

Reversion Request: This action is not allowed as it is outside the current transaction.

After upgrading from Pega 6.2SP2 to Pega 7.2.1, previously working flow action processes are now showing, sometimes randomly, transaction id mismatch errors when submitting.
One example of a button with multiple steps is attached; these have been typically resolved by code updates. PegaSupport shows multiple similar defects, which are typically due to custom scripts / code, especially when occurring after the Finish Assignment task.

This request is to determine a possible hotfix that can revert the Submit / Finish Assignment behaviour to reproduce the working Pega 6.2SP2 functionality, so that Development does not need to review and update each of the multiple application error scenarios independently.

For reference:

https://pdn.pega.com/support-articles/action-not-allowed-it-outside-cur…

https://pdn.pega.com/community/pega-product-support/question/getting-er…

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

Low-Code App Development Case Management Low-Code App Development Upgrades SR Exists
Moderation Team has archived post
Share this page LinkedIn