Screen flow navigation via the breadcrumb causes an exception
A screen flow has been configured to 'Allow Errors' so a user can navigate between screens even though not all of the required fields have been completed. There were a few issues encountered when users' navigated back and forth in the screen flow using the breadcrumb control.
The issues did not occur when using the Back button.
Issue 1: When a user tries to navigate back using the breadcrumb control, an exception occurs.
Issue 2: Once the first issue was addressed, the user could navigate back using the breadcrumb control but then the user was unable to proceed to the next screen using the Next button. When clicking Next, the flow did not proceed to the next screen.
Issue 3: A user was able to submit the flow without all of the required fields being completed.
Issue 1 Exception:
Caused by: com.pega.pegarules.pub.PRRuntimeException: Section 'Screen3' execution error on page 'pyWorkPage' of class 'Org-Work-TestCase'. : Error including section 'Screen3' on page 'pyWorkPage' of class 'Org-Work-TestCase'.
Steps to Reproduce
- Create a screen flow for a temporary work object.
- Check the "Allow Errors" box on the screen flow start shape.
- Configure the screen flow with three flow actions (Screen1, Screen2, Screen3).
- In the Screen3 section, include a radio button that is sourced from a BillingAddress page.
- Run the flow for the work object.
- Click Next to navigate to Screen2.
- Navigate back to Screen1 by clicking the Screen1 breadcrumb.
- Now try to click Next to proceed to Screen2 again.
Root CauseIssue 1: An exception occurred when trying to navigate back using the breadcrumb control because empty classless pages were created when navigating with the breadcrumbs. These pages were referenced by radio buttons in a section used later in the screen flow. When using the breadcrumbs control, all of the sections are validated so an exception occurred for the section.
Issue 2: The user was not able to click the Next button after navigating back due to a defect in Pegasystems' code or rules when the work object is temporary.
Issue 3: The user was able to submit the flow without completing all of the required fields because there were custom activities that cleared the page messages.
Perform the following local-change steps:
Issue 1: Add a visibility condition on the radio buttons so they are only displayed if there are results on the page used to source the data.
Issue 2: Apply HFix-38008.
Issue 3: Update the custom activities so the page messages are not cleared.
0% found this useful