Question
Kaiser Permanente
IN
Last activity: 12 Jan 2018 2:53 EST
System is Showing Error message after Signature Capture
In our application we have a screen where user can provide his/her signature. This is done by using OOTB Capture Signature control. The issue is when user enters his/her signature and clicks on Accept link available there and then submits the screen, system showing the error "This action is not allowed as it is outside the current transaction." On tracing we found that pyStaleTransaction activity is executing in this scenario. By tracing the issue we found that on click on the Accept link in the Signature Capture Control, final activity named "pzAttachSignatureWrapper" (Work-) is getting executed which in turn calls another final activity named "AttachFile" (Work-) where an explicit Commit step is given without any precondition. We private checked out the activity and commented this step and performed above mentioned steps to test. This time there was no error and the provided signature was also captured as an attachment. Since we cannot update/checkout above mentioned activities (all are Final rules) so, we could not check in our changes. Can you help me?
***Updated by moderator: Lochan to update Categories and group tags***
Accepted Solution
Kaiser Permanente
IN
Hi All,
Soumyadip is from our team and we went through a support article in PDN (https://community.pega.com/support/support-articles/transaction-id-mismatch-data-ui-screen-not-getting-saved) yesterday having similar problem and have performed the changes as mentioned there. Now, system is working as expected. Thanks for all your help.
Arnab
Pegasystems Inc.
IN
A stale transaction occurs when attempting to navigate to a previous step of a flow in progress, such as when a user clicks a web browser's Back button before flow completion.
In the event of a stale transaction, @baseclass.pyStaleTransaction is executed and displays the default StaleTransactionMessage for pyMessageLabel:
“This action is not allowed as it is outside the current transaction.”
Is the error observed always ?
Provide the stack trace from the logs to have a look .
Thanks,
Arun
EPAM Systems, Inc.
ES
Hi Soumya,
Thanks for posting on PSC.
I have reviewed associated SR, "SR-C5875" and could see still it's still open and under investigation.
When you will trace down, there is a label "HI" associated with the "Commit" step-35. And it's jumped from whenever there is a failure(Step-23,21 and 16). On further investigation, I found that there is an additional configuration addressing few bugs in Pega 7.3.1 as compare to Pega 7.2.1 of "AttachFile" activity. And it
This step commits the update in history table whenever attachment fails. Ideally, I too feel there should be some pre-condition though not sure what is the special significance that it wasn't added.
As you're able to resolve this issue by commenting the erroneous step-35 and you have already reported this under "SR-C5875". I would suggest to wait for the resolution provided under SR. You could provide this link in the SR for reference who's working on SR.
Hope it helps you in addressing the reported behaviour at your end. Kindly notify by marking this post as answered, if above said information assisted you.
Regards,
Asif
Hi Soumya,
Thanks for posting on PSC.
I have reviewed associated SR, "SR-C5875" and could see still it's still open and under investigation.
When you will trace down, there is a label "HI" associated with the "Commit" step-35. And it's jumped from whenever there is a failure(Step-23,21 and 16). On further investigation, I found that there is an additional configuration addressing few bugs in Pega 7.3.1 as compare to Pega 7.2.1 of "AttachFile" activity. And it
This step commits the update in history table whenever attachment fails. Ideally, I too feel there should be some pre-condition though not sure what is the special significance that it wasn't added.
As you're able to resolve this issue by commenting the erroneous step-35 and you have already reported this under "SR-C5875". I would suggest to wait for the resolution provided under SR. You could provide this link in the SR for reference who's working on SR.
Hope it helps you in addressing the reported behaviour at your end. Kindly notify by marking this post as answered, if above said information assisted you.
Regards,
Asif
Accepted Solution
Kaiser Permanente
IN
Hi All,
Soumyadip is from our team and we went through a support article in PDN (https://community.pega.com/support/support-articles/transaction-id-mismatch-data-ui-screen-not-getting-saved) yesterday having similar problem and have performed the changes as mentioned there. Now, system is working as expected. Thanks for all your help.
Arnab