Extensibility
This section explains the extensibility feature, which helps banks to extend product services for customizing features as per their requirements.
Extension Data Entity Model
The extension data is stored as name-value pair as a part of entity. Since No-SQL database does not support any entity relationships across collections (tables), the extension data is provided as another column in the entity collection or table.
|
Column Name |
DataType |
Description |
|---|---|---|
|
extensionData |
map<text,text> |
extension Data placeholder to store the data as name-value pair |
Extension Data Support in API
Marketing Catalog Microservice supports retrieval and storage of extension data along with the product data. The payload of all the APIs has extensionData JSON node to support retrieval and persistence of data into the extension column as name-value pairs along with the product data.
- POST or PUT APIs support to create or update extension data.
- GET APIs, by default, are extended to retrieve extension data along with the product data.
Extension Data in Design time
"extensionData" JSON node is added to all the input and output schema where the extension is allowed
Swagger
extensionData: type: object
isExtendable" property is set as "true" in entity
Entity
"name": "ProductInformation", "javaPackage": "com.temenos.Microservice.marketingcatalog.entity", "tableName": "ms_marketingcatalog_productinformation", "isExtendable": true,
Extension Data in Runtime
Sample extension data for POST and PUT APIs is shown below.
Sample extension data for GET APIs is shown below.
In this topic