Server Automation Scripts
Within the FintechOS Studio, there are Server Scripts which execute several actions which embody a business need such as: filtering products, returning products and setting amounts or periods. On-demand automation scripts are available for being called from any object or context. Here is a list of the scripts used in this solution.
These scripts manage the data coming from the Companies House Connector. Consider installing the connector.
|
Script |
Type |
|---|---|
| FTOS_BARET_GetApplicationDocuments |
On demand |
| FTOS_BASME_GenerateOnboardingDocuments | On demand |
| FTOS_BASME_GetAvailableBundle | On demand |
| FTOS_BASME_GetAvailableProducts | On demand |
| FTOS_BASME_GetCorporateAddress | On demand |
| FTOS_BASME_GetRetailApplicantId | On demand |
| FTOS_BASME_LinkRetailOnboarding | On demand |
| FTOS_BASME_SendMailOnboardingApplicationDocuments | On demand |
| FTOS_BASME_SendMailPickUp | On demand |
| FTOS_BASME_SendOfficersEmail | On demand |
| FTOS_BNKAP_AddExtraRepresentative | On demand |
| FTOS_BNKAP_AgreeDocument | On demand |
| FTOS_BNKAP_CheckIfIsCustomer | On demand |
| FTOS_BNKAP_CompanyHouseSaveData | On demand |
| FTOS_BNKAP_DeleteExtraProducts | On demand |
| FTOS_BNKAP_GetCompanyOfficers | On demand |
| FTOS_BNKAP_GetCompanyProfile | On demand |
| FTOS_BNKAP_GetCorporateAddressData | On demand |
| FTOS_BNKAP_GetCorporateApplicantByRetail | On demand |
| FTOS_BNKAP_GetCorporateRepresentatives | On demand |
| FTOS_BNKAP_GetExtraProducts | On demand |
| FTOS_BNKAP_InsertExtraProducts | On demand |
| FTOS_BNKAP_OfficerDeleteData | On demand |
| FTOS_BNKAP_OfficerSaveData | On demand |
| FTOS_BNKAP_SaveRetailB2CId | On demand |
| FTOS_BNKAP_SetApplicantSMEApplication | On demand |
This script gets from the entity FTOS_BNKAP_ApplicationDocument records about the documents agreed and signed by the customer based on the applicationID. It is used in FTOS_BASME_AccountApplication in the step ContractSigning.
Input: var applicationId
Output: var data
This script gets the document from the banking product, it checks if there is a documents already, if not it generates the document for the customer. It is used in FTOS_BASME_AccountApplication in the step ChoosePackage.
Input: var accountApplicationId; var bankingProductId; var applicationId
Output: boolean true/false.
This script gets the banking products created with Banking Product Factory and their data and it places the data in the array prodList, element of the object res.
Input: var bankingProductId; var bp; let ic; let com; let cxc; let c; let per; let cv; let curr; let f; let bxb
Output: object res
This script gets the products and inserts them in the array.
Input: var bp; var cl; let scl; let ct; let bs; let ic; let com; let cxc; let c; let per; let cv; let curr; let f
Output: array products
This script maps the address of the SME. It is used in FTOS_BASME_AccountApplication in the step CustomizeCard.
Input: var corporateApplicantDataId
Output: object officeAddress
This script maps the retailApplicantDataId to FTOSBNKAPRetailApplicantDataId. It is used in:
- FTOS_BASME_AccountApplication in the step ContractSigning
- FTOS_BASME_AccountApplication in the step ContractSigning
- FTOS_BASME_AccountApplication in the step Hooray.
Input: var applicationId
Output: var res
This script is
It is used in FTOS_BASME_AccountApplication in the step Hooray.
Input: var retailApplicantId
Output: saves the session and updates the value in retailApplicantId.
(This is the Drop-down text)
It is used in FTOS_BNKAP_CorporateApplicantData in the step InformPartners.
Input: var address; var tokens
Output: sends the email
This script determines whether or not the customer has agreed to the document. It is used in the FTOS_BASME_AccountApplication in the step ContractSigning.
Input: var applicationDocumentId; var value
Output: boolean agreed
This script checks to see if the customer already exists in the database based on the PIN, but it has hardcoded that they do not exist.
Chance the value of the boolean.
It is used in:
- FTOS_BASME_AccountApplication in the step Hooray
- FTOS_BNKAP_RetailApplicantData in the step PersonalInfo.
Input: var PIN
Output: boolean false
This script saves the data coming from the connector.
Input: var corporateApplicantId
Output: updates the data in FTOS_BNKAP_CorporateApplicantData
This script deletes the products. It is used in FTOS_BASME_AccountApplication in the step TailorPackage.
Input: var applicationId; var deselectedProd
Output: deletes by Id the products
Based on the company number, the system returns the associates from the API. It is used in FTOS_BNKAP_CorporateApplicantData in the step CompanyConfirmation.
Input: var companyNumber
Output: N/A
This script imports the library BANFintechOS, and returns the company.
It is used in FTOS_BNKAP_CorporateApplicantData in the step CompanyIdentification.
Input: var companyIdentifier
Output: var finalResp
This script sets the office address. It is used in FTOS_BNKAP_RetailApplicantData in the step CheckYourData.
Input: var retailApplicantId
Output: object officeAddress
This script gets the corporateApplicantDataId by the retailApplicantId.
It is used in FTOS_BNKAP_RetailApplicantData in the step Contact Info SME.
Input: var retailApplicantId
Output: var corporateApplicantDataId
This script gets the pricing for the products. It is used in FTOS_BASME_AccountApplication in the step TailorPackage.
Input: var applicationId
Output: var data
This script inserts banking products. It is used in FTOS_BASME_AccountApplication in the step TailorPackage.
Input: var applicationId; var assocProdList
Output: var assocProdList
This script deletes the data for the officer.
Input: var corporateApplicantId
Output: delete the data in FTOS_BNKAP_ApplicantRelation based on the id
This script saves the representative in the database from the connector.
Input: array officerObj
Output: inserts the data in FTOS_BNKAP_ApplicantRelation
This script gets the representatives from the database.
Input: var corporateApplicantDataId
Output: sets the representatives as the final representatives
This script adds an office in the database, when data is not retrieved from the connector.
Input: var representative; var corporateApplicantDataId; var setAsApplicant.
Output: var retailApplicantId
This script saves the session for the B2C for the representative. It is used in FTOS_BNKAP_CorporateApplicantData in the step CompanyRole.
Input: var retailApplicantId
Output: saves the session in FTOS_BNKAP_RetailApplicantData
This script sets the id for the Retail Applicant Data to use Flow Control. It is used in FTOS_BNKAP_CorporateApplicantData in the step CompanyRole.
Input: void
Output: void
This script send the email with the OTP code.
Input: var address; var tokens; var temlate; var proxyLink.
Output: sends the email
This script sends the email with the documents.
Input: var applicationId; var applicantDataId; var accountApplicationId.
Output: If the email with the documents is/ is not sent, the business status is updated.
Contact Validation
To access the configurations done:
- Open FintechOS Studio.
- Open the main menu Digital Journey, select Form Driven Flows.
- From the list, select the flow named FTOS_BNKAP_ContactValidationSME.
- Click on the section tab named Field Options.
- From the Entity Form Fields, open email and phone from the grid:
| Name | Attribute Change Event |
|---|---|
| phone | The method validatePhoneNumber called by the object validator using the parameters mobilePhone (string of digits, the value) and mobilePhone (the attribute). |
The method validateEmail called by the object validator using the parameters email (string of digits, the value) and email (the attribute). |