What’s New

Search bar in the Menu

FintechOS Portal and FintechOS Studio now accommodate a search bar. It is possible to search for the menu items, not the records inserted. For more details, see Overview.

Clone a Form Driven Flow

In order to save time and effort, it is now possible to duplicate a Form Driven Flow effortlessly. The duplicate will have all the configurations of the original, including all of its characteristics. To only difference is the name. After the cloning process is done, it is possible to change any of the configurations and tail the form to the desired look and functionality. To duplicate a form with all of its data and configurations, click on the pre-existing from, on the General page and click on the button ''Clone form''. For more details, see Creating Form Driven Flows.

Steps triggering Actions on a Form Driven Flow

A complex Form Driven Flow is made up of several steps which lead a client through mandatory information gathering and business processes. For example, add an action step to trigger the generation of a contract once the client has reached that step. To add steps and configure them no-code, several types of steps are available on the platform:

The Action step calls a Form Action configured beforehand and it is called by attaching it to a step and deciding the navigation flow afterwords.

Form Action in a step

After having added an action in Flow Control, a user is able to set multiple formActions that automatically will be triggered after save, before navigation, if a specified condition (similar to navigation rule) is true. There are two grids displayed for configurations After Load and After Save. For example, insert a condition to calculate the eligibility of a potential client in the after save grid. For more details, see Adding and Configuring Steps.

UI Designer

There are several new features in the release in the UI Designer capability of FintechOS Studio. The buttons inserted in the UI Designer can call:

  • custom

  • call custom processor (and endpoints)

  • call form action.

For example, add a button to call the eSign processor and have it be triggered when the client clicks on the button that reads ''Sign agreement''. For more details, see STEP 4. Working with Buttons.

Endpoints input and output mappings in UI designer

When adding a pre-defined endpoint to a button in UI Designer, the output has the Server Automation Script with an output structure set as “Boolean”. For example, the output structure bool could be for a true value bool of a ''Agree to data processing by third-party partner''.

Flow control rule can trigger Checking with custom processor

It is possible to create a rule that checks the attribute mappings of an endpoint to return the values true or false from the bool attribute. For details, see Flow Control.

Business Formulae Object Collection

In an argument data of a complex type with properties A,B,C of type string and D,E of type numeric. The result will be a collection of items with properties A, B and C, where C will be the SUM for the group determined by the content of properties A and B. For details, see Formula Editor.

Copy 
var result = FROM(data).GROUPBY(["A","B"]).SUM("D");

Data Config Deployment

To achieve an import, a package can be xml placed in a zip type archive and import it. It is available from the interface of the FintechOS Studio or through the Package Deployer.

E-sign with tags or coordinates or both

To configure the signing of a document that was either configured with FintechOS' Digital Documents Processor or a document generated externally by a bank of insurance company, it is possible to sign it by placing a tag or with coordinates or both on a PDF file by creating a request. In order to correctly identify where we are adding the signature via coordinates, the SigntureCoordinates object contains: FileName, PageNumber and coordinates X and Y.

Business Workflows transition message

A FintechOS user is able to write a message to be displayed when a transition from a status to another is performed for the user on the FintechOS Portal to read it and be notified of the change. For example, set the message to be displayed in the UI ''Your application has been approved'' to be shown when the application's status has been changed from potential client to approved by an insurance officer. For more details, see Edit Workflow Transition Configuration.