Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

20
Replies
6856
Views
Roberto Burgos Member since 2012 12 posts
Vodafone DE
Posted: Oct 25, 2016
Last activity: Jul 13, 2017
Closed
Solved

Screen Flow Required Fields validation preventing on navigating back

We are on PRPC v 7.2 and currently when Navigating out of a section by clicking on the tab or the circles in either TabScreenFlow or TabScreenFlow7, the required fields validation would fire and prevent you from going back, this behaviour is NOT the same as clicking the back button where you can go back without filling this information. See attached screenshots.

To see attachments, please log in.
User Experience

Posted: 8 years ago

Hello Roberto, 

Thanks for posting your query in PSC. :)

Are you trying to use/click browser back button? If yes, how about using the browser in kiosk mode(or disable these buttons through JavaScript) that restricts them to click browser back/refresh button. Does this help?

Regards,

Rincy

 

 

To see attachments, please log in.
Posted: 8 years ago

Hello Roberto,

Refer below Support article suggesting the local change.

https://community.pega.com/support/support-articles/block-browser-back-button-and-right-click-portal

Refer below URLs in this regard:

Hope this helps.

Regards,

Rincy

To see attachments, please log in.
Posted: 7 years ago

Hello Aileen, 

Thanks for posting your query in PSC :)

Find answer to the below query:

Query: How to check 'Allow errors' option on the start shape?

Answer: Right click on the start shape of the Screen flow. Under Harness name, enable/check the checkbox 'Save on last step'. This will show the 'Allow errors' checkbox. Refer the attached screenshot (from Pega 7.2.2) for your quick reference. This is same for Pega 7.2.

Regards,

Rincy

To see attachments, please log in.
Posted: 7 years ago

Hi Rincy,

Thanks for the help.

By checking these checkboxes, i am able to remove those mandatory field alerts but i am getting errors for those mandatory fields in previous screen at the top

PFA. If this is expected.

Thanks

Saurabh

To see attachments, please log in.
Posted: 7 years ago

Hello Saurabh, 

Thanks for your response. 

Could you share the screenshots of the use case showing the actual behavior. Also, share the configuration made for the screen flow. It will help me to replicate the use case at my end in order to verify the OOTB(out of the box) behavior.

Regards,

Rincy

To see attachments, please log in.
Posted: 7 years ago

Hello Saurabh, 

Thanks for the response. 

From the screenshot snippets, I see that you are using TabbedScreenFlow7 and have 3 assignments(Medicare, Applicant and Product/Plan) configured for the screen flow. While user keeps the required fields blank for the assignment Applicant(2nd screen) and moves back to Medicare(1st screen), then the validation errors are displayed on 1st screen. So, here the user clicks on the back button. Is my understanding correct? If yes, I do not see this behavior in Pega 7.2.2 with TabbedScreenFlow7. However, with TabbedScreenFlow harness, I see the validation errors on the 3rd screen when the user clicks on the next button.

Flow configured at my end is as below:

Start > DisplayInfo > CollectInfo > DisplayInfo > End

(OR)

Start > Approve > CollectInfo > DisplayInfo > End

If I modify the screen flow to add Assignment (having FlowAction as  Approve) instead of the 3rd screen, then I do not see the error on the next screen

Show More

Hello Saurabh, 

Thanks for the response. 

From the screenshot snippets, I see that you are using TabbedScreenFlow7 and have 3 assignments(Medicare, Applicant and Product/Plan) configured for the screen flow. While user keeps the required fields blank for the assignment Applicant(2nd screen) and moves back to Medicare(1st screen), then the validation errors are displayed on 1st screen. So, here the user clicks on the back button. Is my understanding correct? If yes, I do not see this behavior in Pega 7.2.2 with TabbedScreenFlow7. However, with TabbedScreenFlow harness, I see the validation errors on the 3rd screen when the user clicks on the next button.

Flow configured at my end is as below:

Start > DisplayInfo > CollectInfo > DisplayInfo > End

(OR)

Start > Approve > CollectInfo > DisplayInfo > End

If I modify the screen flow to add Assignment (having FlowAction as  Approve) instead of the 3rd screen, then I do not see the error on the next screen

Modified flow:

Start > DisplayInfo > CollectInfo > Approve > DisplayInfo > End

Does this help?

Regards,

Rincy


Show Less
To see attachments, please log in.
Posted: 7 years ago

Hi Rincy,

While navigating back from second screen i.e. Applicant assignment, the user is clicking on Medicare (Assignment). When we are clicking on next button, we are getting the required alert for the mandatory fields.For the same required fields we are getting errors on the top of the page while moving back.

Tried by changeing the screenflow as well. It didn't work.

Thanks

Saurabh

 

To see attachments, please log in.
Posted: 7 years ago

Hello Saurabh, 

Thanks for informing that you have raised the SR. Could you please share the SR number for tracking purpose.

Under the raised SR, assigned Support Engineer will coordinate with you for the requested screen share.

Regards,

Rincy

 

 

To see attachments, please log in.
Posted: 7 years ago

Hi, 

Can you please provide a screenshot of the Strat Shape, where i need to enable allow errors.?

I am not getting the Allow errors option anywhere.

Thanks

Saurabh

To see attachments, please log in.

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

Pega Collaboration Center 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