Hi all
I am following Appian standard in using a text field on a form with which to populate a decimal field in my rule input.
Appian standard behavior for a decimal field is that if a comma symbol is used to indicate a decimal place, the symbol is automatically removed and the value is then displayed with no separation.
Example:
The user enters 650,52
On refresh, the comma disappears and the value saved in the rule input is now 65052
If one uses the period symbol, the value is displayed correctly, thus 650.52, and the value is saved correctly into the rule input
We cannot assume that the target group of users will understand the distinction between the symbols, so we need to put in some sort of validation in order to avoid the issue.
I have tried using the cleanwith() function, but am unable to make it work.
I would like to be able to do one of the following (in order of preference):
Any help will be greatly appreciated!
Discussion posts and replies are publicly visible
My immediate thought in that case would be to find 1 or 2 that are especially common for the purpose of a lingua franca for the country. It might be English, which is becoming the lingua franca of the whole world. Then there's the question of how British or American do you get with the English.
You've got a nice can of worms here.
Thanks Mike
A bit beyond my skill level and our deadline at present, but definitely on the agenda down the line.
Thanks for your input, and have a great weekend!
For this reason (the use case with multiple commas) it may be better to use your #3 suggestion (validation) instead of replacing the commas with periods because you're less likely to encounter weird edge cases like this.
Yes, I believe the same. It's more safe and easy to build as he will avoid many different scenarios that need to be covered during the number typing.