We are working on a requirement to trigger authentication mechanism for anonymous user (unauthenticated user) by launching local action pyReAuthGadget to capture user credential and to authenticate the user.
On post submit of this local action, expected scenario is the browser session will be refreshed and then authenticated user portal is displayed but no browser refresh is happening, unauthenticated user portal stays the same.
To refresh the browser session post submission of local action, we included reload harness and window.location.reload() as well, still there is no session refresh.
With this approach, getting following error due to stale transactions.
“This action is not allowed as it is outside the current transaction”
Also we replaced reloadBrowser function with ReloadHarness activity to refresh portal harness. This too didn’t work. “This action is not allowed as it is outside the current transaction” message is displayed.
Thanks for the solution! We are able to resolve this issue.
Previously we placed the Login button (that launches pxReAuthGadget local action) in temporary work flow context, which resulted in stale transaction. To overcome this we placed the login button (that launches pxReAuthGadget local action) in portal header, browser refresh is working successfully.
We updated pyReauthenicateForBasic (one of the calling section in pxReAuthGadget local action) - Login button action set, to call reloadBrowser function.
@bhavanasahithi The approach 2 seems to be right. I’m using the same approach and it did not give me that error. Is your action calling reloadBrowser first then refresh section (which is OOTB and should be there when you did save as)
