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

Screen flow previous button not responding in obfuscated IAC

SA-654

Summary



IAC gadget is included in a page which triggers a screen flow. The screen flow previous button brings user to the previous screen in PRPC but in IAC gadget it does not respond. This only happens when obfuscation is enabled.

Error Messages



Not Applicable 

Steps to Reproduce



Setup IAC

Enable obfuscation on both IAC and PRPC (see more info below)

Setup a screen flow
Access creating new work object with a flow that has screen flow
Click on previous button

Quick steps to enable obfuscation

1) Add the following lines into prconfig.xml in PRPC.
        <env name="initialization/nodetype" value="webtesting"/>
        <env name="initialization/urlencryption" value="true"/>

2) In IAC gadget, set pega.web.config.encrypt=true; (the default is false)

For more information see 
https://pdn.pega.com/internet-application-composer/deploying-iac-v31-for-web-access


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. That the previous button calls for pega.u.d.submit to pass URL parameters. The URL parameters are obfuscated, but the '\' at the end of the URL parameter is obfuscated as well.


Resolution



A local change was given to the customer (see below), however a dev tip has been created 
BUG-167063 and targeted for Pega 7.1.7.

1) Create a custom function in UserWorkForm
     function Custom_goToPreviousTask(activity, prevAssn) {
          var activity = "pyActivity="+activity+"&previousAssignment="+prevAssn;
          pega.u.d.submit(activity);
     }

2) In the previous button's configuration, go to the actions tab. Change the onClick event's action to have that custom function, passing the activity and previous assignment as parameters.
For example the default value as shown in TabbedScreenFlow7 harness:
       onClick Event's Action: Run Script
       Function Name: script:pega.u.d.submit

       Parameter Name: <empty>
       Parameter Value: "pyActivity=GoToPreviousTask&previousAssignment=true"


Change to the following:
       onClick Event's Action: Run Script
       Function Name: Custom_goToPreviousTask

       Parameter Name: pyActivity
       Parameter Value: "GoToPreviousTask"
       Parameter Name: previousAssignment
       Parameter Value: "true"

Published March 29, 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