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

 Nandini Vanjavakam (NandiniVanjavakam)
Wells Fargo
Software Engineer
Wells Fargo
IN
NandiniVanjavakam Member since 2013 11 posts
Wells Fargo
Posted: Nov 6, 2019
Last activity: Nov 7, 2019
Posted: 6 Nov 2019 9:22 EST
Last activity: 7 Nov 2019 9:03 EST
Closed

"Disabled" - Enable client side validation checkbox not working as expected at flow action level.

We have a requirement to not fire browser validations in some screens, therefore we thought of disabling the "Enable client side validation" checkbox at flow action level.

As all other screens will have to fire client side validation, we left the "Enable Client side validation" checked at harness level.

But the flow action changes are not reflecting and validations are still fired.

Please suggest.

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Low-Code App Development
Case Management

Posted: 5 years ago
Posted: 7 Nov 2019 9:03 EST
Geeda Ilango (GeedA)
Pegasystems Inc.
Technical Solutions Engineer
Pegasystems Inc.
IN

For your requirement "To not fire browser validations in some screens"

Are your mentioning the browser validation pop-up similar to below screenshot?

Kindly provide the screenshot of the issue to look further.

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