Question
GovCIO
US
Last activity: 3 Dec 2019 14:23 EST
Required field validation need not be fired on backwards flow navigation
Hi Pega Experts,
We have the requirement to navigate back from a Tabbed screenflow without checking the mandatory fields validation on the UI screen using Pega V722. For that, we did a small research and we got the below PDN article to resolve this issue.
After we check the function from the above post, we noticed that this function is being called from a FINAL rule:Navigation (HTML Fragment) under RSV=>Pega-EndUserUI:07-10-23. We have done a private edit on this to add the above mentioned function changes directly and we were successful in resolving the issue. But we are afraid of making this FINAL rule changes in our RSV to proceed further. We would like to know Pega confirmation on whether we can bring this function change in our RSV or can we get a Pega fix (HFix/Sol) in the mentioned RSV above? Also, we don't want to get any new issues after making the code changes based on this final rule across the application. I forgot to mention that we have the same application running on the mobile native app and we don't want to get any impact on the mobile side after incorporating the changes mentioned above. Please advise and we are creating an SR on this to get Pega direction on this particular requirement.
Thanks,
Ravi Kumar Pisupati.
Hi Pega Experts,
We have the requirement to navigate back from a Tabbed screenflow without checking the mandatory fields validation on the UI screen using Pega V722. For that, we did a small research and we got the below PDN article to resolve this issue.
After we check the function from the above post, we noticed that this function is being called from a FINAL rule:Navigation (HTML Fragment) under RSV=>Pega-EndUserUI:07-10-23. We have done a private edit on this to add the above mentioned function changes directly and we were successful in resolving the issue. But we are afraid of making this FINAL rule changes in our RSV to proceed further. We would like to know Pega confirmation on whether we can bring this function change in our RSV or can we get a Pega fix (HFix/Sol) in the mentioned RSV above? Also, we don't want to get any new issues after making the code changes based on this final rule across the application. I forgot to mention that we have the same application running on the mobile native app and we don't want to get any impact on the mobile side after incorporating the changes mentioned above. Please advise and we are creating an SR on this to get Pega direction on this particular requirement.
Thanks,
Ravi Kumar Pisupati.
***Edited by Moderator Marissa to update platform capability tags****
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
GovCIO
US
Hi Rett,
The issue got resolved with local changes mentioned below though Pega Engineer created a FDBK request(FDBK-64336) for this. An email was sent to you on this as well.
Current application behavior:
TabbedScreenFlow7 (Harness) => Header (custom control) for tabs display =>Navigation of all the tabs (back & forth)
Based on the above info keep in mind, we have done the below changes at our end to resolve this issue.
1) Header control rule calls =>Updated existing our custom rule:NestedTabbedNavigation7 (R-O-H)
2) NestedTabbedNavigation7 rule calls => OOTB rule: FormNavigation7 is replaced by our custom rule: <APPNAME>FormNavigation(R-O-H)
3) <APPNAME>FormNavigation rule calls => updated the OOTB rule: Navigation(R-H-F) by calling our rule: <APPNAME>Navigation(R-H-F)
4) <APPNAME>Navigation rule calls => updated with the below function code mentioned in the PDN article:
Thanks,
Ravi Kumar.
Pegasystems Inc.
US
If you do raise an SR for this topic, you will likely be directed right back to the PSC as this is how to/requirement type of query.
On the start shape of the screen flow you can check "allow errors", but I believe that will allow you to navigate both forward and backward without validation. So this may not meet your requirement.
To isolate this behavior for only the backward direction, sounds like an enhancement if there is no OOTB option to configure this. The SA you found outlines a custom approach by overriding one of our functions.
As you also found, this is bound by a FINAL rule, so the only way to do this is to override the entire function in a place like UserWorkForm.
GovCIO
US
Thanks Rett for the response.I got the similar idea to override this function from UserWorkForm but no luck before posting this query. Will try one more time. Here is the SR-D66047 created on this.
Accepted Solution
GovCIO
US
Hi Rett,
The issue got resolved with local changes mentioned below though Pega Engineer created a FDBK request(FDBK-64336) for this. An email was sent to you on this as well.
Current application behavior:
TabbedScreenFlow7 (Harness) => Header (custom control) for tabs display =>Navigation of all the tabs (back & forth)
Based on the above info keep in mind, we have done the below changes at our end to resolve this issue.
1) Header control rule calls =>Updated existing our custom rule:NestedTabbedNavigation7 (R-O-H)
2) NestedTabbedNavigation7 rule calls => OOTB rule: FormNavigation7 is replaced by our custom rule: <APPNAME>FormNavigation(R-O-H)
3) <APPNAME>FormNavigation rule calls => updated the OOTB rule: Navigation(R-H-F) by calling our rule: <APPNAME>Navigation(R-H-F)
4) <APPNAME>Navigation rule calls => updated with the below function code mentioned in the PDN article:
Thanks,
Ravi Kumar.