Decimals - pega's client-side validation triggers before custom scripts
In my locale, decimal separator is ',' and there is no grouping separator. We have a script connected to harness which replaces all '.' with ',' in decimals, in case the user inputs the wrong separator.
The script works fine on first input. The problem we found with Chrome is, if you edit an input field twice and enter a decimal with a '.', pega's built-in clientside validation, "webwb pega_validators js", triggers before the script and displays "x.x is not a valid decimal value" error despite the '.' being replaced at the same time.
How can we solve this issue? Disabling clientside validation in harness is undesirable.
***Edited by Moderator: Pallavi to update platform capability tags***