Support for `Money` with multiple components

[homedirectory]

Description

In TG it is possible to use component types as property types. One of the supported component types is Money. Class Money declares several properties, all of which can be used to represent the internal structure of Money values. As with all component types, the actual representation of Money (i.e., the actual internal structure) is determined from configuration at runtime. This configuration is manifested in the Hibernate type mapping. A mapping for Money defines the set of components that are enabled and can be persisted in and retrieved from the database.

While the platform provides several Hibernate type mappings for Money, only one is fully supported -- Money with amount only. Full support encompasses EQL, domain metadata and other smaller sub-systems.

The goal of this issue is to provide support for Money representations with multiple components (i.e., more than just amount). This task is broken down into the following sub-issues:

• 1. Money with multiple components: EQL and domain metadata #2675

• 2. Context-dependent currency for Money properties #2677

• 3. Mapping between currency codes and symbols.

  • Custom currency symbols should be displayed in the UI.
  • Users should be able to search by currency symbols.

• 4. Ability to override Hibernate type mapping configuration #2679. This will enable applications to configure the required Hibernate type for Money.

• 5. Multiple currency symbol Web UI support #2684

Change overview

To be reflected in the sub-issues.

Expected outcome

Comprehensive support for Money with multiple components.