Question
GDPR Erase
Last activity: 7 Oct 2019 2:47 EDT
Currency symbol in the input field of number controls - Product enhancement
We need a way to show a currency symbol in the input field of number controls. We want to use native input controls of mobile devices and have a currency symbol appear in the input field after the user entered the numbers via the native number control (the number in the the input field should look something like this: "1.000,00 €"). If we would use another control like text, we could add the currency symbol to the input field field, but the native number control wouldn't appear anymore on mobile devices. Additionally the user shouldn't be able to enter any other letters, symbols etc. in the field.
Pegasystems Inc.
US
You can use the default currency control.
Go to presentation tab -> Editable Format
Change the type to Number, and select "Display value using read-only formatting" checkbox.
The property gets the currency symbol based on the locale specified(see attached gif)
GDPR Erase
We can't add a currency symbol automatically to the input field if we use any type of number / currency / etc. control which sets type=number in the markup. The requirement is pretty specific and the currency symbol needs to be part of the input field while the user types.
Pegasystems Inc.
US
If I may, what is the business justification for the requirement?
There are some technical limitations you are facing here, not to mention user experience issues. How is the symbol determined? Is the user supposed to enter the symbol? If so, are you supposed to test that the symbol entered is correct? In order to place any commas or periods in the proper place, you will need to know the currency ahead of time and the proper format for the currency. While entering, you will not know the proper placement of some of the symbols until the user has completed entering the digits as the placement is determined by the number of digits entered.
Unless there is a solid business justification, I do not understand why you would spend the money to implement something this complex when something simpler should suffice.
I do not mean to hijack your thread, but sometimes, I think it is necessary to push back on a requirement if there is not sufficient business justification, especially when it seems the business is specifying design rather than functionality.
Hope this helps!
GDPR Erase
Thank you for your answer.
I have to agree with you there completely and we did push back on the requirement outlining the impact on the plattform. Nevertheless business still wants that feature.
Pegasystems Inc.
US
It appears that are some examples of using the telephone input control for this.
Hopefully the following link will be helpful.
https://ux.stackexchange.com/questions/67323/mobile-money-input-easiest-method