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

Press Backspace causes "Action not Allowed" error



When a user is working on a flow and accidently presses the backspace key outside of a text field, the application goes back to the previous step.  When the user attempts to proceed in the flow again they see an error message.  They must re-open the work item to get back to a working state, discarding any changes they may have made.

Error Messages

"This action is not allowed as it is outside the current transaction."

Steps to Reproduce

  1. From some point inside the application, press the backspace key outside of a text box or use the browser back button to return to a previous step.
  2. Attempt to move forward in the flow again.

Root Cause

This is caused by operator error - Pega is a stateful web application, not a stateless web page. By forcibly moving the client side to a different page (via the browser back function, which is also be triggered by hitting the backspace key) when leaving the "current transaction." Actions that require a transaction with a clear start and end will give the mentioned "outside the current transaction" error if you attempt to leave them and return to them later.


The following local-change disables the usage of backspace to prevent users from accidentally making this operator error.  

Add this javascript to the UserWorkForm:


document.onkeydown = function()


    var t=event.srcElement.type;

    var kc = event.keyCode;

    return ( (kc !=8) || (t == 'text') || (t == 'textarea') || (t =='password') )



Published August 31, 2015 - 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