FintechOS Release 24.4.1

October 22nd, 2025

This release introduces new features in the Platform such as Dex AI Assistant and Product Factory improvements, support for Open Telemetry, as well as new features for Backoffice Insurance, such as Non-chronological Alterations, Policy and Master Policy Backdated Cancellation, and Coverage Management Enhancements.

See below the main highlights of FintechOS 24.4.1 release:

What's New

Policy Administration

See below the main highlights and read the detailed release notes in the Policy Admin page:

  • Policy and Master Policy Backdated Cancellation

    Backdated cancellations ensure accurate coverage dates, correct billing, and smoother customer experience. For this to be possible, new calculations accommodate refunds for clients for uncovered periods and compensation amounts to cover costs for insurers.

  • Non-chronological Alterations

    A new capability that provides greater flexibility when managing mid-term adjustments (MTAs). With this enhancement, changes can be applied directly to the active policy based on operational needs, without requiring a strict time sequence.

  • Future-Dated Alterations and Payment Recalculation

    When a future-dated policy alteration is created and an installment is invoiced before its effective date, the original payment schedule is invalidated and automatically recalculated.

  • Extending MTA and Renewal for Multiple Formulas

    Enabling multiple formulas per product significantly boosts pricing flexibility and operational efficiency, leading to faster product launches, more accurate risk assessment, and ultimately increased revenue and customer satisfaction.

  • Formula Mapping for Alteration and Renewal

    When using the resolve mapping for input to call the Product Factory, it will also reuse the same resolve mapping for the result to save those values on the configured fields.

  • Approval Logic on Alteration

    You can now configure an approval step for specific alteration types within the Mid-Term Adjustment (MTA) process. When a request includes at least one alteration that requires approval, it will enter the new Pending Approval status. Only users assigned the appropriate security role, defined per alteration type, can approve, decline, or edit the request.

  • Lapse and Suspension Improvement

    A new field has been added to payment statements to show the exact date when a policy will officially end if payment isn’t made. This date is automatically calculated when the statement is created, based on the due date, any grace period allowed by the payment type, and any suspension time.

  • Coverage Management Enhancements

    The coverage validity period and the amount included in the total premium are displayed directly on each version, so you no longer have to do the calculations yourself.

    When a coverage or sub-coverage is removed, its end date is automatically set to one day before the MTA effective date.

    The coverages grid now shows only coverages valid as of the MTA effective date, while the additional coverages grid highlights optional coverages not currently on the policy.

    Renewed policies now include only the coverages valid at renewal, each ending precisely on the policy’s end date.

  • Update to Master Policy Alteration Handling

    The system now automatically transitions any draft alteration to an inactive state if a new policy is added or an existing policy is cancelled under the master policy.

  • Improvements

    The Alterations Summary section, displayed after updating the due date of master policies, now shows a list of all installments along with their old and new due dates.

    Refactored views for Policy and Master Policy Payment Types, Insured Objects, and Policy Parties to display their valid from/to dates.

    Improved reliability and performance by updating the FTOS_PH_ProcessAsyncEvents scheduled job to get all unprocessed events and send them to async. This job now runs every second.

API Improvements

  • FTOS_PYMT_InsertStatementDueDate job is no longer available. At upgrade, you should adopt the new API FTOS_PYMT_GenerateStatementAPI.

  • FTOS_CB_StartLoanSubmissionFlow_AsyncEngine, API for digital process of submitting a loan application into the loan management system, received an update that includes the isSuccess: true or false response, with the message: "Your Request has been received" if true, and an error message if false. In addition, the input nextStage is now optional. If someone doesn't provide it, the system will automatically use createCustomer as the default.

  • The FTOS_INSP_UndoCancellation API, which post is used to Undo(move to status Cancelled) a Cancellation request via API, is now renamed to FTOS_INSP_RevokeCancellation.

  • The FTOS_INSP_RequestCancellation API accomodates the new changes to the cancellation functionality for both policies and master policies. The former FTOS_INSP_RegisterCancellation will be deprecated.

  • The new FTOS_PYMT_GenerateOutgoingPaymentRequest API is used to insert a new outgoing payment request on the new data model.

  • The new FTOS_INSP_ValidateCancellation API is used for approving a cancellation. It supports an optional paymentDetails object with keys: paymentBeneficiaryType, bankCode, and paymentIBAN, inheriting standard interface behavior.

Product Factory

See below the main highlights and read the detailed release notes in the FintechOS Platform 24.4.1 page:

  • Formula-Based Deductible Amounts and Indemnity Limits

  • Character Limits for Text Fields in the Product Designer and Product Settings

  • Test Product APIs Locally

  • APIs for Retrieving Deductible and Indemnity Limits

  • Audience Validation in the Get Available Offers API

  • Renamed Payment Schedule Types Settings for Better Clarity

  • Product Formulas Stability Enhancements

  • Get Offers API Deprecation

Dex AI Assistant

  • Compact View for Long Dex Replies

  • Message Copy Buttons

  • Multi-Context Responses

  • Improved Context Resolution for Banking and Insurance

  • Updated Chat History Layout

  • Zoomable Images

Platform Improvements

  • Skip Failed Records in Data Imports

  • Attach Imported Records to the Correct Business Workflow

  • Services Catalogue

  • Sort Option Sets Alphabetically

  • Include Order Index When Retrieving Option Set Items from Cache

  • No-Label Attribute Fields

  • Improved Debugging for Formula Tests

  • Lock Discriminant Details After Data Set Versioning

  • Endpoint Name Validations

  • Alternative Navigation in Form-Driven Flows Without Saving Data

  • JQueryUI Upgrade

  • GetEntitiesMetadata API Performance Optimization

  • Open Telemetry Logging Support

  • Null values for parameters

  • Users for Running Jobs

  • Azure AD Integration Update

Mandatory Changes

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

This 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.

Deprecation of Current User Session History Method

The ebs.getCurrentUserSessionHistory Client SDK method has been deprecated. While the method remains functional for backward compatibility, it is no longer recommended for use in new implementations.

Deprecation of Visual Studio Code Cloud Instance

The Visual Studio Code cloud instance has been deprecated. Although the feature remains accessible, developers are encouraged to transition to the local developer sandbox for code editing.