Configuration
The Temenos Digital Assist application comes with optimal out-of-the box functionality. However, by using Spotlight application, you can configure the functionality of certain features. For some configurations, you can make a few changes at the microservice level. This section contains the configurations made at the microservices level.
Line of Business attribute in Origination Processing Microservice
Line of Business Attribute in Origination Processing Microservice
Introduction of Line of Business attribute in Origination Processing MS to,
- Distinguish applications of various lending journeys
- Setting entitlements
Origination Processing MS is used for processing the SME and Retail lending applications post their submission and for this to work, an attribute, LineofBusiness is introduced to differentiate the lending applications at the Request and Facility levels, and to determine user permission to access a request. The channel through which the loan is applied passes this attribute and the same is stored at the Request and Facility level in the application. This attribute has the following values:
- Retail
- SME
The user permission to access a request is also determined by this attribute. For example, a user with Retail RM role can only view a request that has Retail attribute value in it.
Response code
"Corporate" value present in "Line of Business" attribute for any request submitted through Assist application.
{
"parentProcessId": "2397",
"requestOverView": {
"requestId": "R202128339089",
"dealId": "R202129676711",
"partyId": "2116729669",
"groupId": "",
"arrangementId": "",
"relationshipManager": "bfleck",
"purposeId": "",
"usageId": "",
"amount": 1000000.0,
"currencyId": "USD",
"profitCenter": "",
"branchId": "",
"portfolioId": "",
"requestStatus": "01",
"LineofBuisness": "Corporate",
"requestDate": "2021-06-16 08:14:36.000",
"lastChangeUserId": "",
"requestName": "HTC Corporation",
"lastChangeDateTime": "2021-06-16 08:14:44.000",
"activeProcessId": "2398",
"withdrawalReasonType": "",
"withdrawalReason": "",
"canWithdraw": true,
"extensionData": {}
}
"SME" value present in "Line of Business" attribute for any request submitted through an application.
{
"parentProcessId": "2397",
"requestOverView": {
"requestId": "R202128339089",
"dealId": "R202129676711",
"partyId": "2116729669",
"groupId": "",
"arrangementId": "",
"relationshipManager": "bfleck",
"purposeId": "",
"usageId": "",
"amount": 1000000.0,
"currencyId": "USD",
"profitCenter": "",
"branchId": "",
"portfolioId": "",
"requestStatus": "01",
"LineofBuisness": "SME",
"requestDate": "2021-06-16 08:14:36.000",
"lastChangeUserId": "",
"requestName": "HTC Corporation",
"lastChangeDateTime": "2021-06-16 08:14:44.000",
"activeProcessId": "2398",
"withdrawalReasonType": "",
"withdrawalReason": "",
"canWithdraw": true,
"extensionData": {}
}
"Retail" value present in "Line of Business" attribute for any Facility submitted under a Deal through Assist application.
{
"facilityId": "F202038204993"
"dealId": "R202129676711",
"partyId": "2116729669",
"groupId": "",
"arrangementId": "",
"relationshipManager": "bfleck",
"purposeId": "",
"usageId": "",
"amount": 1000000.0,
"currencyId": "USD",
"profitCenter": "",
"branchId": "",
"portfolioId": "",
"requestStatus": "01",
"LineofBuisness": "Retail",
"requestDate": "2021-06-16 08:14:36.000",
"lastChangeUserId": "",
"requestName": "HTC Corporation",
"lastChangeDateTime": "2021-06-16 08:14:44.000",
"activeProcessId": "2398",
"withdrawalReasonType": "",
"withdrawalReason": "",
"canWithdraw": true,
"extensionData": {}
}
The user permission to access a request is determined by this attribute. For example, a user with Retail RM role can only view a request that has Retail attribute value in it.
http://localhost:7002/ms-entitlement-api/api/v1.0.0/system/entitlements/users/:userId
{
"entitlements": [
{
"resources": [
{
"resourceCategory": "saving",
"resourceFilter": "lineofBusiness=01",
"roles": [
"CorporateRelationshipManager"
]
}
]
}
]
}
{
"entitlements": [
{
"resources": [
{
"resourceCategory": "saving",
"resourceFilter": "lineofBusiness=01",
"roles": [
"CorporateUnderWriter"
]
}
]
}
]
}
{
"entitlements": [
{
"resources": [
{
"resourceCategory": "saving",
"resourceFilter": "lineofBusiness=01",
"roles": [
"CorporateOperations"
]
}
]
}
]
}
{
"entitlements": [
{
"resources": [
{
"resourceCategory": "saving",
"resourceFilter": "lineofBusiness=01",
"roles": [
"CorporateSupervisor"
]
}
]
}
]
}
Mapping application data from ODMS to Origination Processing MS and Party MS
Mapping Application Data from ODMS to Origination Processing MS and Party MS
ODMS to Origination Processing MS
After a lending request application (retail or SME) is submitted in the Origination application, the request application data received in Origination Data Storage microservice (ODMS) is mapped to the corresponding fields in Origination Processing microservice and for the remaining ODMS fields (data) for which there are no corresponding fields in Origination Processing MS, new fields are created in Origination Processing MS, so that Temenos Digital Assist application gets the data from Origination Processing MS.
The Temenos Digital Assist application retrieves the request application data from Origination Processing MS. Remaining data for which there are no corresponding fields in Origination Processing MS, Temenos Digital Assist application receives the data from ODMS MS for the given application ID (Request ID).
For the ODMS-Origination Processing MS field mapping, refer to the enclosed document (compressed file in .zip format). note that this document is for reference purpose only.
ODMS to Party MS
After a lending request application (retail or SME) is submitted in the Origination application, and post Customer Review task is completed for a Prospect (applicant or a co-applicant), all the prospect data are automatically copied from ODMS and stored in Party MS and the Party ID is created in Party MS. This occurs through an auto-task that will create a party entry in Party MS and store all the information related to the prospect. The Temenos Digital Assist application receives the newly created Party ID.
In this topic