Prerequisites
Before you start mapping, complete the following tasks:- Verify whether the integrated system supports adding custom fields.
- Review the available fields in both Banking OS and the integrated system to identify gaps or discrepancies.
- Determine whether you need any additional fields in the integrated system, then integrate them.
- Identify which custom fields are necessary and map them in the Banking OS transformation source file.
Map fields
To map data fields, connectors use JOLT or XSLT transformations depending on the inbound data format accepted by each target system:- JOLT transformations: JSON inbound data. See JSON fields.
- XSLT transformations: XML inbound data. See XML fields.
common-templates.xslt or credentials-and-device-info.xslt file. The available files depend on the connector you use. Add the transformation file content that your deployment needs to the values.yaml file in the sources section of your live project repository. For more information about the values.yaml file, see Connector repository and configuration.
JSON fields
To map data fields that use JSON data formats, use the JOLT transformation library. To add or update a mapping, edit the JOLT transformation source file.Example mapping scenarios
The following table shows example mapping scenarios for fields in Banking OS and the integrated system:Field available in Banking OS only
The following JOLT mapping sends the work email address from Banking OS to a custom field in the target system:Field available in the target system only
The following JOLT mapping reads thedaysLate field from the target system into the Banking OS customFields object:
Field unavailable in both systems
The following JOLT mapping maps a new Banking OS custom field to a new custom field that you add in the target system:Custom JOLT transformations
The Banking OS custom JOLT transformation operation is available in the Banking OS generic connector library. You can use it to build custom data transformations that align JSON data from the integrated system with the Banking OS output format. The following table lists the available Banking OS custom JOLT transformation operations:
The DateTime transformation converts incompatible DateTime values from target systems to UTC format in the Banking OS output. To use this transformation, specify the source date fields that require conversion and provide the preferred DateTime format.
The following example shows a DateTime transformation:
XML fields
To map data fields that use XML data formats, use the XSLT transformation library. To add or update a mapping, edit the XSLT transformation source file.XML mapping scenarios
The following table shows example mapping scenarios for fields in Banking OS and the integrated system:XML field in both systems
The following XSLT mapping writes the Banking OSnotes field to the Description element in the target system:
XML field in the target system only
The following XSLT mapping writes the Banking OScustomFields.createdByUser field to the CreatedByUser element in the target system:
Custom fields
Custom fields let you access data or attribute values that the Banking OS Unified API may not cover. Use custom fields to extend the APIs to suit your specific requirements. Banking OS core banking connectors include predefined fields with a wide range of attributes for each core banking system. If you need more fields than the predefined fields, add them to thecustomFields object.
Supported data types
A custom field is aMap<String, Object> that supports the following data types:
Link custom attributes
To link your custom attributes to core attributes, edit the mapping files. Manage this configuration in thevalues.yaml file in the sources section of your live project repository. For instructions about mapping custom fields between Banking OS and the core banking system, see Map fields.
Valid custom field structure
The following example includes five custom field attributes and their corresponding values:Invalid custom field structure
The following example is invalid because theaddress field contains a nested object, which custom fields don’t support: