Installing SME Digital Lending and Underwriting

Follow the guidelines below to install and configure SME Digital Lending and Underwriting 1.0.0.

Prerequisites

1. Install and configure:

   • SySDigitalSolutionPackages v22.1.4001.zip

   • FTOS Platform v22.1.4 (with B2CPortal, B2CProxy, JobServer, OpenAPI v3)

   • Banking Product Factory 4.0

   • dotnet-scvutil on FintechOS Studio and on the Portal where the solution is deployed.

2. Import the packages for the following integrations: Company House, Ideal Postcodes and Experian (you can find these connectors in the Connectors 22.1.4.zip archive file available on Release Hub).

3. Install the Codat Connector.

4. Unzip the SME Lending Assisted v1.0.zip archive file and import the BAN-CDM, BAN-CDM-CAO, BAN-FOD, BAN-SDK, and BAN-FAQ packages available in the prerequisites folder.

   

5. Check that the items contained in the FTOS_DBK_Common asset are not linked to any other digital asset:

   • Attribute companyStatus on the Corporate Applicant Data entity.

   • Workflow Library FTOS_BAN_GeneralHelper

Install the Solution

Add the latest syspackdeployer in the solution folder, edit the installer and run it in admin mode.

The packages available in the solution folder contain the following assets:

Package	Assets
01.FTOS_DBK_SQLBefore	FTOS_DBK_SQLBefore
02.FTOS_DBK_DataModel	FTOS_DBK_DataModel
03.FTOS_DBK_Resources	FTOS_DBK_Resources FTOS_DBK_Common
04.Lexis Nexis	LexisNexis
05.FTOS_DBK_Data	FTOS_DBK_Data
06.FTOS_DBK_Data_BankingProduct	FTOS_DBK_BP
07.FTOS_DBK_SQLAfter	FTOS_DBK_SQLAfter

 

Post-Installation Setup

1. Go to Vault – platform system parameters and update as follows:

   • sys-compatibility-url-params-router

   • sys-single-page-app-router

     Both parameters must contain the following JSONs:

     Copy

      {"portal":"Digital Banking RM","value":"0"},{"portal":"BAN-B2C","value":"0"}

   • sys-hide-app-dashboard

     Set to 1 on portal Digital Banking RM.

2. In Vault, add the following settings for Portal:

   Key Name	Value
   core-setting-portal-profile	Digital Banking RM
   FTOS_DBK_CodatApiUrl	https://app-ecos-apache-camel-test.azurewebsites.net/services/api/codat
   FTOS_DBK_CorporateStructureMock	{"ParRegNumber":"999998","TreePosition":"2","TotalNumSubs":"1","TotalElements":"3"}"}
   FTOS_EXTD_EXPE_baseUrl	https://sandbox-uk-api.experian.com/risk/business/v2
   FTOS_EXTD_EXPE_ClientId	1
   FTOS_EXTD_EXPE_ClientSecret	*Experian client secret*
   FTOS_EXTD_EXPE_DelphiBaseUrl	https://sandbox-uk-api.experian.com/risk/consumer/v1
   FTOS_EXTD_EXPE_DEV	1
   FTOS_EXTD_EXPE_Password	*Experian password*
   FTOS_EXTD_EXPE_UrlOAuth2	https://sandbox-uk-api.experian.com/oauth2/v1/token
   FTOS_EXTD_EXPE_UserName	*Experian username*
   FTOS_EXTD_POST_ApiKey	*IdealPoscodes client secret*
   FTOS_EXTD_POST_ApiUrl	https://api.ideal-postcodes.co.uk/v1
   lexn-client-id	FintechOSUKTest
   lexn-password	*LexisNexis password*
   lexn-role-type-role	Administrator
   lexn-role-type-user	*LexisNexis role type user*
   lexn-url	https://staging.bridger.lexisnexis.eu/LN.WebServices/12.0/XGServices.svc/Search
   lexn-user-id	*LexisNexis user id*
   OpenAPI_BaseUrl	The OpenAPI app service base url. E.g.: "https://app-openapi-ban22-qa.azurewebsites.net"
   OpenAPI_Password	qweQWE123!@#
   OpenAPI_User	api.caller
   SMTP:EnableSSL	0
   SMTP:Host	*SMTP host*
   SMTP:Password	*SMTP password*
   SMTP:Port	*SMTP port* - usually "587"
   SMTP:User	*SMTP user*
   CompanyHouseApiKey	*Companies House api key*
   CompanyHouseApiUrl	https://api.company-information.service.gov.uk
   B2CProxy	B2C url.

3. Add the following app settings in the b2cportal section in Vault.

   Key Name	Value
   feature-b2c-userjourneys	1
   feature-b2c-userjourneys-api-key	API_KEY mentioned in step 5.
   feature-b2c-userjourneys-impersonated-user	b2c.guest

4. Navigate to FintechOS Studio and create a user with the above mentioned data in the OpenAPI_User and OpenAPI_Password fields and assign them the FTOS_DBK_ApiCaller role.

5. Configure the B2C Proxy as follows:

   • Add the following in the b2cproxy app service > proxy > proxy.config.js:

   Copy

   if (output.path === "/Agreements") {
       output.path = "/Main";
       output.query += "#/customform/FTOS_BASME_ConfirmAgreements";
       return output.redirect();
   }

   • Navigate to Anonymous Frontends and make sure there is a record with the same name and api key as mentioned in the proxy.config.js file, on the line where request headers are set. E.g.: output.requestHeaders.set("NAME", "API_KEY");

   • Open this record and make sure the custom flow FTOS_BASME_ConfirmAgreements is published.

6. Import the custom files into their respective app service and folder, as described in the custom files folder structure.

   

7. Navigate to portal profile > Digital Banking RM and add the company logo: ftos_logo_light.png. The logo is available in the uploadEBS folder.

   

8. Navigate to FintechOS Studio/Main#/entity/FTOS_BP_Agreement/list and insert the following data:

   Code	Name	Display Name
   200	gdpr	GDPR Agreement
   201	marketing	Marketing Agreement
   202	relative	Relative with Bank Employee
   203	information	Information Agreement
   204	affiliates	Affiliates Agreement
   205	business	General Business Agreement

9. After creating each agreement, insert a record in the Banking Products view, having the same code as the agreement and the Banking Product CL. Attach them to the CL banking product.

10. Run the sql files from the sql after manual changes folder.

    

11. Navigate to FintechOS Studio> Banking Factory > Banking products, select the CL code and enter the following records in the Formula Engine > Banking Product Formulas section:

    Name	Formula Type	Formula	Data Mapping
    FTOS_DBK_CheckAgreementsAnswers	Agreements	FTOS_DBK_AgreementsAnswers	FTOS_DBK_AgreementsAnswers%
    FTOS_DBK_CheckEligibility	Eligibility	FTOS_DBK_CheckEligibilityQuestions	FTOS_DBK_CheckEligibilityQuestions%