This action is not allowed as it is outside the current transaction
Hi,
I am getting below error when trying to close the attachment window using 'Close' button. Pega version is 7.1.7
'This action is not allowed as it is outside the current transaction'
Attached is the HTML source code used for this control. Application was migrated recently from 5.5 to 7.1.7 and this functionality was working fine in 5.5. Could you please suggest a solution as soon as possible
Message was edited by: Lochan to add Category
Pegasystems Inc.
AU
Hello Rintu,
Could you please elaborate on the use case? are you deleting the attachment prior closing the attachment window?
We have a HFix-20526 for the use case if you are deleting the attachment prior closing the attachment.
Commonwealth Bank of Australia
AU
Hi Basavaraj,
I am attaching a document before closing the window. Document is getting attached succesfully but getting this error if the window is closed using 'Close' button.
Pegasystems
US
Use the trans-id-mismatch error from your pega log to know the TIME the error happened, and the OLD and NEW transaction id.
Keep in mind that every time there is a commit, a NEW transaction error is generated.
Within the response of your fiddler sessions, search for the OLD transaction id (use CTRL-F in fiddler to find it!) . The first place that appears in a response is where that id got generated due to a commit and became the ONLY valid transaction id.
use STATISTICS feature in fiddler to see WHEN each session actually happened.
Use TIMELINE in fiddler to see overlap of the sessions.
Search for the NEW transaction id in the fiddler sessions. The first place that appears in a response is where that became the ONLY valid transaction id.
When you do CTRL-F, you can see where the OLD transaction id appears in the URL. The place where it appears AFTER it is no longer valid is where you'll get the trans-id-mismatch error.
SUMMARY: Whenever the trans-id is passed in the URL from browser to Pega, Pega checks it and gives a trans-id-mismatch error if it is wrong. Pega often shows the CORRECT trans-id in the RESPONSE to the browser. If a commit occurs during that fiddler session , the trans-id CHANGES (I think a fiddler session corresponds to a Pega "interaction").
/Eric