I recently faced an issue while using an Edit Input rule for converting user input to uppercase. The configuration was done correctly, but I did not get the expected output during runtime.
The Edit Input function is supposed to convert the entered value to uppercase, but the field is not consistently reflecting the transformed value as expected. I verified the Edit Input configuration multiple times, and the Function appears to be correct.
I wanted to understand whether this could be:
• a configuration issue
• a Constellation/UI behaviour limitation
• a client-side vs server-side execution issue
• or a possible application/product bug
Has anyone faced a similar issue with Edit Input rules for uppercase conversion in Pega?
Any suggestions or insights would be helpful. Thanks!
Edit Input rules do not work in Constellation. It is definitely not your configuration issue. The reason I am thinking is that the UI is rendered in Constellation in the browser itself just from the JSON metadata received from Pega. Edit input rules we write are Java code. As browser cannot compile Java code, that functionality is not possible. For it to be possible, the approach would be to make a call to server for every character entered in the input fields, run the code in server and replace the input with the response. As this is not a usable approach, I think this functionality is omitted. This is just my understanding, Experts @MarcCheong@Kamil_Janeczek please let us know the exact reason for it or point us to the documentation if it is already mentioned somewhere.
Anyhow, Edit Validate rules work because the validation happens once, we save or submit the form, at the server itself and the error is returned in the API response.
