Mandatory Changes from v18 to v24

If you're looking to upgrade from FintechOS Platform v18 to v24, then check out below the list of mandatory changes and deprecated features:

Mandatory changes

  • The B2C proxy server is retired, and Anonymous Frontends are deprecated. The Upgraded Anonymous Frontends, also known as B2C Portals, have replaced the legacy anonymous frontends which are no longer supported. See the dedicated migration guide for information on how to transition to the new frontends.

  • IDP features might trigger mandatory changes

  • Products defined in the legacy Product Factory still work, but can no longer be versioned. If you wish to version a legacy product, you need to recreate the product in the new Product Factory, along with any formulas and product admin configurations. The new product will have a different product code.

  • If using FintechOS Loan Management, please revise your product admin configurations after the upgrade. If you create new banking products in Product Factory, whether you've upgraded Loan Management or this is your first installation, keep in mind that you must create product service configuration records within Loan Management for all the banking products intended to be used in contracts.

  • Legacy Product Factory APIs for pricing and checking the underwriting rules no longer work on insurance products that have pricing set at the sub-coverage level. Use the following APIs instead:

  • WSDL (SOAP) APIs are no longer supported. FintechOS Platform WSDL APIs and WSDL Web API client libraries have been discontinued. Instead, you can use Service Pipes for your WSDL integrations.

  • Legacy authentication has been phased out. The FintechOS Identity Provider is the only supported identity and access management method. For information on how to migrate your user accounts, roles, and business units to the FintechOS Identity Provider, see the dedicated migration guide.

  • Deployment packages are no longer supported. Use digital solution packages and configuration data packages instead.

  • Custom and Custom-on-demand folders can no longer be renamed.

  • The kv/<environmentName>/<portalName>/app-settings/core-setting-portal-profile Configuration Manager key used to assign a portal profile to a FintechOS Portal instance has been replaced with kv/<environmentName>/<portalName>/app-configurations/portal-profile

  • policyStatusChangeAPI, used to change the status of the policy and update, if needed, some details about the policy, received an update, the policyValidityType, policyValidity, and policyBeginDate keys are removed, along with the logic that recalculates policyEndDate. The pricing remains based on the validity, and these changes do not impact the premium amount.

  • File Uploads to Virtual Attributes No Longer Supported in B2C Portals

    The 2 24.4.1 release introduces a security validation that allows users to upload files in B2C Portals only within the context of a specific file attribute. This prevents file uploads to custom data extensions, as ownership settings cannot be applied to virtual attributes.

  • Workaround: Use a regular file attribute instead of a virtual file attribute for the scenarios where virtual attributes were previously used. E.g.: Use a button to upload a file to the regular file attribute, pass the file to an endpoint, then clear the file attribute from the UI.

  • As a result of the Configuration Manager introduction in R2, system configurations such as system parameters, API keys, or service credentials are no longer stored in the database. Customizations that read these settings directly from the database (e.g. via stored procedures) must be refactored accordingly.

  • The new FintechOS Identity Provider authentication layer requires all user accounts to have unique email addresses. User accounts that do not have a valid email address or that have duplicate email addresses will not be migrated to the new authentication provider.

  • FintechOS Identity Provider as the default authentication layer for the FintechOS applications and services. The FintechOS Platform Identity Provider is not compatible with APIs before v22. A Legacy API with FintechOS Identity Provider Authentication has been developed to allow you to easily refactor existing API calls to work with the new identity provider.

  • Starting with 22.1 (R2), all client scripts (afterGenerate, fetch) are executed under the “use strict“ policy.

  • Starting with Studio v22.1.5, invariant dates are immutable. Refactoring is required to update the addDays, addMonths, and addYears methods values.

  • Task Management

    • v4.0 - Release 22.R3

      • If Operators decide to work on a task allocated to another colleague, they can click the Pick Up button, and the system changes the Assignee to the new Operator. The behavior is modified from the previous version, where the initial task was closed and a new one was created. Now a history table is in place with all the Assignees over time.

      • The ClosedReallocated status has been removed, but the old tasks that are already in the ClosedReallocated status remain the same. Also, the status transition from AllocatedButHoliday to ClosedReallocated is no longer available.

  • Loan Management (Core Banking)

    • 4.0 (22.R3) - Due to the numerous changes performed on the banking product type dictionaries coming with Banking Product Factory v4.0 we had to create copies of our existing repayment schedules. After installing Core Banking, you'll notice that some repayment schedules are split into Secured and Unsecured Loan banking product types. Make sure you verify each repayment schedule definition and see to which banking product type it is applicable.

    • 4.1 (R3 Update Pack 5) - Within the FTOS_CB_AddUpdateContract endpoint, the contractPeriod input parameter's type changed from String to Numeric. Make sure you perform the necessary updates to your integration calls.

    • 3.3 (22.S) - All our Core Banking endpoints were reworked and are now compatible with the OpenAPI 3.0 standard. Make sure you update your integrations accordingly, changing the authentication request, placing the received bearer token into the Authentication header of each request, and updating the endpoint request syntax as described in the new Core Banking Developer Guide.

    • Please note that the following endpoints' output variables were changed to comply with the upper camel case naming convention:

      • FTOS_CB_AddUpdateIndividualCustomer

      • FTOS_CB_AddUpdateLegalEntityCustomer

      • FTOS_CB_AddUpdateCustomerBankAccount

      • FTOS_CB_AddUpdateCustomerCollateral

      • FTOS_CB_AddUpdateCustomerLimit

      • FTOS_CB_ApproveCustomerLimit

      • FTOS_CB_ApproveCustomerCollateral

      • FTOS_CB_AddUpdateEarlyRepayment

      • FTOS_CB_ApproveEarlyRepayment

      • FTOS_CB_ApproveReturnedAmountOrGoods

      • FTOS_CB_AddUpdateReturnedAmountOrGoods

      • FTOS_CB_AddUpdateContractDocument

      • FTOS_CB_ApproveContractDocument

      • FTOS_CB_GetRescheduleOverduesNotifcations

      • FTOS_CB_GetCustomerLimitVersion

      • FTOS_CB_GetContractRepaymentSchedule

      • FTOS_CB_GetContractData

        The input variables for FTOS_CB_AddUpdateContractDocument and FTOS_CB_ApproveContractDocument were also changed to comply with the camel case naming convention.

    • 3.1 (22.W) - Custom repayment plans can now be added to contracts for cases when the existing Core Banking logic is not compatible with the desired schedule. New role-based limit capabilities allow you to manage limits for different customer roles, such as merchants.

  • FintechOS 22 Update Pack 1 - Unique constraints have been added in the data model to the following entity attributes.

    Entity Attributes
    scheduleTrigger name
    scheduleService name, scheduleTriggerId
    securityroleitem entityId, securityRoleId, securityOperationId, securityScopeId

Several user interface settings are now set using system parameters instead of web.config keys. On upgrade, you need to manually set up any system parameters corresponding to existing web.config keys that have been deprecated.

Old web.config key (deprecated) New System Parameter
feature-hide-my-profile-link sys-hide-my-profile-link
feature-hide-user-settings sys-hide-user-settings
feature-move-language-to-user-profile sys-move-language-to-user-profile
feature-right-footer-text sys-right-footer-text
feature-hide-company-logo sys-hide-company-logo
feature-hide-menu sys-hide-menu
feature-hide-search-in-menu sys-hide-search-in-menu
feature-feeds-hearbeat-interval sys-feeds-hearbeat-interval
feature-approval-task-heartbeat-interval sys-approval-task-heartbeat-interval

Deprecated

  • Deployment packages are no longer supported.

  • The B2C proxy server is retired

  • WSDL (SOAP) APIs are no longer supported.

  • (Legacy) Anonymous Frontends are deprecated.

  • Legacy authentication has been phased out - FintechOS Identity Provider is the only supported identity and access management method.

  • Legacy web.config settings for Blob storage are no longer supported and must be configured via Configuration Manager.

  • Legacy web.config settings and the EbsLogs.ApiLog database storage schema for API logging are no longer supported. For information on how to set up API logging, see the Administration Guide.

  • The sendAsync, useDefaultSender, from parameters of the sendEmailNoEx server SDK function have been removed.SendMail and sendMailNoEx method signature has been changed, with email queues managed by job servers.

Single Customer View (Customer 360) - starting with 22.R2

  • Starting with this version, the below Single Customer View endpoints are implemented. These endpoints replace obsolete Core Banking customer endpoints related to creating or updating legal entities or individual customers, addresses, customer representatives, and groups. For additional information see the Private Individuals Endpoints, Legal Entities Endpoints, and Customer Endpoints pages.

    • FTOS_ACC_CB_AddUpdateIndividualCustomer

    • FTOS_ACC_CB_AddUpdateLegalEntityCustomer

    • FTOS_ACC_CB_AddUpdateCustomerAddress

    • FTOS_ACC_CB_AddUpdateCustomerRepresentative

    • FTOS_ACC_CB_AddUpdateCustomerGroup

    • FTOS_ACC_CB_AddUpdateCustomerGroupMember