The Mx Model Reflection module can be used to show the reflection of the configuration in your domain model. The module creates an object for each entity, attribute, and reference.
1.1 Typical Use Cases
The typical usage scenario is selecting and showing entities from your domain model to use for another configuration.
After importing the module, add USE ME > MxObjects_Overview to the navigation of your app. Run your application for the synchronization. You are able to enable synchronization for each module. For both security and performance purposes, you do not want your entire domain model structure available in your app.
If you have a large app, the synchronization will take much longer.
2.1 Token Configuration
The token configuration used in the Email with Templates module now also allows you to specify the display pattern. This allows you to configure how the attributes are shown rather than relying on the defaults of the module.
The display pattern in the token is optional. If you do not specify a value, the module will use the original behavior.
For attributes of the decimal type, the display pattern
DecimalFormat is used (for more information, see Class DecimalFormat).
For dates, the
SimpleDateFormat is used (for more information, see Class SimpleDateFormat).
For all other attributes, the functions from java.util.Formatter are used (for details on the patterns, see Class Formatter).
All the patterns use the locale from the context. Based on the user’s language, the pattern will change its behavior if necessary.
2.2 Display Pattern Example (Using En_US Lanuage)
- Long attribute with a thousand separator:
- Date attribute:
2nd of July 2016
- Decimal attribute with a thousand separator of 2 decimals: