Extending Transact APIs
Interaction Framework brings users and financial resources together through a flexible and RESTful architecture. You can create Provider APIs to expose a required core banking business function as a RESTful API. The Provider APIs require artefacts in Transact (Version or Enquiry).
This section explain how you can manage Version and Enquiry through Workbench and provides the following features to boost productivity of the Transact APIs.
- API Inheritance: Extends an existing API to adapt behavior.
- User Field Propagation: New custom data model fields are automatically propagated to an API payload without the need to update the API.
Temenos Workbench supports inheritance feature that helps an API to inherit the fields and behavior of a parent API.
Automated User Field Propagation for APIs
Transact APIs can leverage the ability to automatically add new user fields to selected APIs. This feature is optional.
This section explains how to search, create or edit a new extension between a Transact API and rules created in Rule Engine, regular expressions for basic field level validations, python script validation or field defaulting with constants.
This section explains how to search, create or edit a new extension between a UXP Browser operation and python script validation.
This section explains how to create a new Regular Expression validation, search and edit an existing Regex.
This section details about creating and editing Python Script to have customized validations as per the user needs.
Regex Validation for Version Fields
This functionality helps to validate IRIS API request fields. It loads all the values from the config microservices and place it in the cache before invoking the Transact API request.
Rules Validation for Version Fields
Rule Engine is a dedicated rules server running on a different or same host. It is not an IRIS component. IRIS must be informed of the location with the credentials to access it. IRIS only supports single rule for each version of an API against domain and operationId. Rules Engine evaluates rules and defaults values to the payload that is sent for the evaluation.This section helps you to configure and run a rule engine, invoke the rules against the API payload and validate the payload.
Rules Validation for UXPB Fields
This section allows you to define your own rules against the UXPB operation. This enables the rules validation for UXPB before performing any operation in Transact, if the applicable rules are for a specific resource.
In this topic