Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Activity is not triggering on button as expected



User has a harness, from where one launches a modal dialog.
From the modal, user clicks a button to run an activity, however the activity is not triggered as expected. Activity does get triggered on the button only for the first time after log in.

User must log off and log back in to run that activity again.

Error Messages

Log message shows "Error: posted transaction id 'XXXXX' for frame 'ABC' does not match record 'YYYYY'".

Steps to Reproduce

  1. Configure a harness with a button to launch a modal window.
  2. Configure button on modal window to run activity.

Root Cause

An issue in the custom application code or rules. The specific design of the user to make a commit which changes the transaction id on the server.

But, that was not returned back, for it to use the new transaction Id going forward.

Hence, the log contained the transaction mismatch id error which did not allow any further processing, also the activity did not execute.


Perform the following local-change: 

Essentially, once a commit is made, user must get the new transaction Id that the server returned.

In PRPC 6.2 SP2, the pxClientExchange parameter is not available to pass the transaction Id back to the client.

So to get the new transaction Id:

1. Create a new non-autogenerated section with the script below.
This enables the URL object to return the transaction id that the server created, back to the user through its response.

pega.u.d.url = '<pega:url ><pega:option name="long"/></pega:url>';

2. Include the above section in the existing modal dialog section.

Published June 2, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us