Dependencies
The correct functionality of Loan Management custom endpoints depends on a series of parameters that take their values from option sets. These option sets that act as dictionaries should exist in your FintechOS Studio environment, as they come along with the Loan Management deployment package.
Dictionaries are sets of allowed values from where a parameter can take one value at a time.
Dictionaries for Customer Endpoints
The table below explains the correspondence between custom endpoint parameters and their possible values:
| Custom Endpoint Parameter | Option Set in FintechOS Studio | Possible Values via Endpoint |
industry
|
Industry
|
|
addressType
|
Address Type
|
|
accountRelationType
|
Account Relation Type
|
|
bankAccountType
|
FTOS_BNKAP_BankAccountType
|
|
expirePeriodType
|
PeriodType
|
|
productType
|
bpProductType
|
|
collateralType
|
Name attribute from FTOS_BP_CollateralType entity |
|
currencyCode
|
N/A | e.g. EUR, USD, RON, LBP |
exchangeCurrencyCode
|
N/A | e.g. EUR, USD, RON, LBP |
limitType
|
Name attribute from FTOS_CB_CustomerLimitType entity |
|
country
|
N/A | This should contain the name of the country. All values must be imported into FintechOS Studio. |
district
|
N/A | This should contain the name of the district. All values must be imported into FintechOS Studio. |
city
|
N/A | This should contain the name of the city. All values must be imported into FintechOS Studio. |
bankCode
|
N/A | This should contain the bank code. All values must be imported into FintechOS Studio. |
productCode
|
N/A | This should contain the banking product code. Values must be set in FintechOS Studio when adding banking products. |
Dictionaries for Contract Endpoints
The table below explains the correspondence between custom endpoint parameters and their possible values:
| Custom Endpoint Parameter | Option Set in FintechOS Studio | Possible Values via Endpoint |
participantRole
|
FTOS_CB_ContractRole
|
|
blockReason
|
FTOS_CB_BlockRoleReason
|
|
covenantResolution
|
Name attribute from FTOS_CB_CovenantResolution entity |
|
productInterest
|
Name attribute from FTOS_BP_Interest entity |
Values must be set in FintechOS Studio when adding banking products. |
paymentScheduleType
|
Name attribute from FTOS_BP_PaymentScheduleType entity |
Values must be set in FintechOS Studio when adding banking products. |
periodicityType
|
Name attribute from FTOS_CB_PeriodicityType entity |
|
installmentMethod
|
FTOS_CB_InstallmentCalculationMethod
|
|
managingBranch
|
Name attribute from business unit |
Values must be added on FintechOS Studio initialization. |
productCode
|
N/A | This should contain the banking product code. Values must be set in FintechOS Studio when adding banking products. |
covenantName
|
N/A | This should be the name of the covenant. Values must be added on FintechOS Studio initialization. |
feeName
|
Name attribute from FTOS_BP_Commission entity |
Values must be set in FintechOS Studio when adding banking products. |
status
|
N/A |
|
graceTypeId
|
N/A |
|
eventReason
|
N/A |
|
DocumentType
|
FTOS_BNKAP_DocumentType
|
|
Dictionaries for General Endpoints
The table below explains the correspondence between custom endpoint parameters and their possible values:
| Custom Endpoint Parameter | Option Set in FintechOS Studio | Possible Values via Endpoint |
entityName
|
N/A | This should contain the name of the entity. All values must be imported into FintechOS Studio. |
recordId
|
N/A | This should contain the id of the record whose business status is going to be changed. All values must be imported into FintechOS Studio. |
businessStatusId
|
N/A | This should contain the id of the business status you wish to change into. All values must be imported into FintechOS Studio. |