FintechOS Release 24.2

September 19th, 2024

This release of the FintechOS Platform unveils the Journey Designer, a robust tool featuring an easy-to-use graphical interface for creating detailed digital journeys across a user’s entire experience on a digital channel. The Journey Designer allows you to map out a high-level overview of the digital journey, facilitating previewing, testing, and stakeholder approval before the development phase starts.

See below the main highlights of FintechOS 24.2 release and read the detailed release notes in the FintechOS 24.2 page:

What's New

Journey Designer

Key features of the Journey Designer include:

• Contextual linking - Link products, actors, and channels to your journey to enhance context and receive relevant options during the design process.
• Comprehensive design elements - Incorporate user interface screens, navigation rules, integrations, back-office tasks, underwriting/eligibility checks, document generation, or omnichannel messages.
• Workflow integration:
  • Preview the journey to visualize the user experience and secure stakeholder approval before development.
  • Annotate each design element with detailed specifications, such as descriptions, validations, UX definitions, or error handling, then automatically generate a fully-formatted Functional Specifications Document (FSD) in line with the "Product is the Spec" philosophy.
  • Publish the journey to automatically generate an associated mock-up form-driven flow, complete with steps, navigation rules, and actions, to jump start the development process.

Product Factory Improvements:

• New Product Templates

  • Property Insurance for Business - You can now service business customers looking to insure properties or buildings.
  • Personal Accidents - Allows you to provide insurance policies to individuals and their beneficiaries in the event of injuries, disabilities, or death resulting from an accident.

• Bundle Insurance Products in Offers

• Adjustable Precision for Loan Installment Calculations

• Support for Optional Coverages and Sub-Coverages in Insurance Products APIs

• Enhanced Performance in Pricing APIs for Banking Products

Digital Journey API v2 Enhancements

• Two new API endpoints have been added to initiate and resume anonymous user journeys
• The start journey, start journey with external ID, next step, and previous step API requests have been enhanced to return current step data in the response (field values, step actions, properties, etc.).

Business Service Components

Business service components help with a better organization of server automation code in medium and large projects. They come with three modules:

• Data Service: for defining functions, inserting or updating data, calling data, run database queries or execute database tasks.

• Business Logic: this layer contains the core logic of the code and supports SDK methods for importing libraries, uploading files, calling reports, changing business status, and more.

• Routes: can be used to import modules from other server side components by referencing the module name.

Code Design Improvements

The below improvements were introduced to aid with following by standard coding practices:

• Custom Events

• Custom Data Ownership

• Improved Separation Between Data Model and Form Fields

• Standardized Event Handler Parameters

• App Data Logic and Code Segregation

• IntelliSense Enhancements

• New getExceptionMessage SDK Method

Digital Packages Enhacements

• More Configuration Items for Digital Assets

• Execute Maintenance Scripts after Digital Solution Package Import

• Improve Checked Out Files Naming in FintechOS Explorer

• Identify Locked Files Faster

Mandatory Changes

Service banking and insurance solutions, also known as backoffice solutions, only work with Jint v3 JavaScript engine. Make sure to follow the instructions on this page for enabling Jint v3.

The upgrade to the Jint V3 JavaScript engine, causes some mandatory changes which you can mitigate by following the instructions in this guide. The switch can be made by configuring a specific system parameter.

The ebs.addFormChangeEvent function in the Client SDK function now accepts a single optional input parameter for its event handler function that conforms to the IChangeHandlerParam interface.