Question
Cognizant
US
Last activity: 12 Feb 2020 8:33 EST
Disable FA submit button until user enters all the required fields
Requirement for an application on customer service for financial services framework on 8.1:
Until user enters all the required fields, the submit button should remain disabled.
There are multiple assignments with this requirement and they usually have about 10 required fields.
Approaches followed:
1.Disable the FA buttons, build customize buttons for each screen-however this approach doesn’t support reusability
2.Tried to write a java script that picks mandatory fields in current screen - the HTML code for the required fields used a Pega’s custom attribute called “validation type =required”-Couldn’t proceed with this.
3.set a display flag on FA submit button (enabled disable condition on client)..on each required field set and action set - on change -post value, run DT. The DT Checks if all the required fields have value in the particular assignment .if yes, set display flag to true. This works but when user clears the required field value the submit button doesn’t get disabled.
Conclusion:
None of these approaches worked for us. Please advice if we missed out any other way.
***Edited by Moderator: Lochan to update platform capability tags***
Areteans
IN
Based on your 3rd approach, I have an idea that may help.
1) Create an Integer property
2) upon change of every required field, call a generic activity or DT which takes an input param (required property name).
3) Activity/DT should check that required field should not be empty. If it's true, increment the integer property. If false, decrement it.
4) In the end, int property value should be equal to the number of required fields.
5) Put the Submit button in a separate dynamic layout which should have a Refresh condition which checks that Int property = no of required fields.
6) Add the disable condition expression for the Submit button as Int property should be less than no of the required fields.
This way, whenever all the required fields are filled, Dynamic layout refresh condition will be evaluated first and then disable condition of the submit button.
I hope this helps!!.
Cognizant
US
Hi Nagendra,
Thanks for your inputs, I see a scenario where we may have an issue:
Say we have a required field FirstName.
User enters the required field value . On change it calls the DT to set the integer property.
Now, User clears the value in First name, since its a required field there is validation that shows up and still the clipboard hold the First Name value, it doesn't clear the value. as a result the submit button will remain enabled.
Areteans
IN
Whenever a user clears any required field, the onChange event will be triggered and DT will be called. So you may need to decrement the integer property whenever the param is empty or null.
So the total count will not be equal to the total number of required fields and the button will be disabled.
condition on the button should run on client or you can use the refresh section on change should also work.
Cognizant
US
When user clears any required field, there is a required error msg that shows up, and the new update is not posted to clipboard.
Yes, on change the DT will run but with the previous field value
Areteans
IN
If the error is showing for empty required field means there is somewhere the validation is happening with empty property value. Finding that should help.