Invalid date entry throws com.pega.pegarules.pub.runtime.IndeterminateConditionalException error
Got a date field wherein text entry is enabled for ease of date entry. If a user enters an invalid date/date format, i.e., special characters or alphabets or more digits than a date should contain, then, com.pega.pegarules.pub.runtime.IndeterminateConditionalException: ** PropertyValueInvalidnull.pegaToBigDecimal() error is thrown. This seems to be a defect in Pega OOTB rules. So, is there a fix available for the same? Error message screenshot is attached.
Note: The said error occurs on submission of such date format, i.e., server side error.
***Updated by moderator: Lochan to add SR details***
The validation depicted by you, is it a client side error or a server side? Because the error we received was on server side, i.e., on submission of data. On client side, we are good with tooltip errors.
Yeah Sravanthi, we are facing client side validation error on such invalid entry.
Though there exists the client side validation to indicate the user about wrong entry, a user can still click submit button on the screen (scenario wherein a user may not see the screen with error and click submit), a farce scenario which exists. This is when such a issue occurs. So, is it not supposed to be handled on the server side in the same way as it is handled on the client side? To sum it up, would like to know if there is any OOTB solution available for the same?
When there are client side validation errors on screen and if you try to submit you should get an alert saying to correct the flagged fields before submitting the form and the same behavior is seen at my end also.
You should not be able submit the form also. I don't understand why is the exception coming at your end.
Could you try defining Refresh action on change of the Date field and check if the issue is still seen. In Mean while I will try to understand why this exception is coming.
The context is not a total form submission or a flow action but rather a refresh section to display further data based on previous data entries and run requisite validations along with it through activity. So, not sure if the alert applies to this context since we aren't getting the same in pega 7.2.1 (upgraded version) or pega 5.5 (older version - same issue exists).
Have tried refresh section on change of date field but this doesn't help.
Observation: Post Value doesn't post the errant date formatted value to clipboard nor does refresh section/post value posts the error message generated out of this.
I see that the issue was due to configuration of the section in the portal harness instead of the flow rule. The resolution was to configure on click Run Script on button click and to add the below code in the UserWorkForm.