Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Using the Currency Control

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

The autogenerated control can display a selected currency using its symbol, code, full name, or ISO code. However, for readability, the decimal separator and thousands separator come from the locale. In addition, if the currency is displayed as a 3-digit code, it can show the ISO code before or after the amount (and optionally delimited by a forward slash):

$ 1,000.00

1,000.00 $

USD 1,000.00

1,000.00 USD

1,000.00 /USD

When the currency is set to display the local currency, the currency of the users locale is displayed.

Implementation

The enhanced currency control contains options for presentation of amount fields in the harness or section, when the currency itself is stored in a separate field from the amount value.

The currency is saved as a numeric currency code (such as 840 for U.S. dollars). The numeric codes are maintained by the ISO 4217 currency code standard. Pega also subscribes to SWIFT directories that list the valid currency codes. The currency codes change infrequently.

Each currency code is associated with a 3-letter text code (such as USD) or the currency symbol (such as $). Only the decimal separator and thousands separator come from the locale. The rest of the displayed data comes from the data lookup, where the 3-character code, currency symbol, number of decimal places, and so on, are obtained.

For example, if the value is 2000.00 EUR, a user in Germany sees the value as 2 . 000 , 00 EUR, and a user in the United States sees it as 2 , 000 . 00 EUR – the same currency but with different decimal separators, according to the convention used for each locale.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us