FintechOS 20.2.1

This release enriches the platform's capabilities with a set of new features and improvements, as well as various bug fixes. Among others, you now benefit from a Payment Processor Service to include payment methods in your Digital Journeys, call the Formula Engine via no-code approach, and create ready-for-export data packages which contain an entity with all its attributes and constraints. Continue reading for more details on what this release has to offer.

IMPORTANT!
FintechOS Studio version 20.2 and greater requires .NET Framework 4.7.2.
When upgrading from previous versions:
  • Update the web.config file to support .NET Framework 4.7.2. For details see .Net Framework 4.7.2.
  • Configure any system parameters that have replaced web.config settings. For details, see New System Parameters.

What's New

Digital Journey Map

A Digital Journey is a set of steps and decision points which take the users throughout a process, carrying them from one step to another. It has multiple flows, such as a client and operator flow.

In order to see all flows together and rules for transitions between steps, the map makes it available to add flows, access and configure each step, perform actions, delete a step, or make modifications to the journey. The map's utility facilitates the process of building complex digital journeys with multiple form driven flows to be navigated, and to include several automation processors or matrices as well in each step. This overview picture of the flows with their steps is useful for the navigation and orientation between the parts of a digital journey. For details, see the FintechOSUser Guide.

Custom Processor Step

FintechOS offers a large variety of micro-services with embedded AI, making it possible for the user to build fully automated digital journeys.

A new type of step has been introduced to the form driven flow configuration. Two types are available: default and processor. When creating a new step in a digital journey, a user can choose to call a processor in that step by selecting the type of processor, as well as the configurations made for that particular processor. For example, a user can build a processor-type step by selecting the eSign processor and the processor's settings, followed by the navigation rules. For details, see FintechOSUser Guide.

Calling the Formula Engine via no-code

This automation processor uses different inputs in order to generate desired outputs. You can implement multi-step calculations using a variety of data types and built-in functions.

After defining the formula input with its arguments and defining its expression, it is possible to call the formula using a no-code approach by executing the formula in form actions within a digital journey. For each step, add the formula executed in the action. This process is effortless for any user. For example, for calculating a complex eligibility formula, you can trigger the calculation of the age formula on the secondary step, and the calculation of the salary in the third step. For details, see the FintechOSUser Guide.

Data packages deployment

This feature makes it possible to create packages for export based on an entity and its attributes with their constraints.

When you need to transfer data and metadata from one environment to another and include the values for the said attributes, the feature makes it easy to export the chosen data, and to import it into another instance of FintechOS, safely and in record time. The user builds a new package by selecting the information he wishes to have in the package. Large packages are downloaded locally and imported later on into a different FintechOS Studio instance, either in the same database or a different one, depending on your needs. For details, see the FintechOSUser Guide.

Data Pipes web.config key

This feature allows our consultants to connect with data such as online or on-premise applications, databases, and Web APIs. After connecting, you can replicate it in the FintechOS database. The 150 data sources available ensure a wide variety of sources for all needs. Data pipes make it undemanding to create a connection with the providers of data access solutions.

Starting with this release, in order to have the Data Pipes up and running, this key is added to the web.config file in Studio: <add key="core-setting-cdata-proxy-url" value="http://192.168.30.18:7090" /> (the value should be changed accordingly). For details, see FintechOSUser Guide.

Payment Processor Service

This new feature makes it possible to add payment methods for a complete Digital Journey. Once a client is in the final stages of a journey, it may require them to make a payment, therefore, a payment service will be configured by inserting the name of the service in the web.config file. Hence, a user can pay for a service online with a seamless integration of a payment method in a journey.

Fixed Issues

Summary Module
When a user tried to add a new formula argument of object type, the formula input mapping control did not work correctly showing a null error. FintechOS Studio
Modifications to the initial value from the mapping input was not saved correctly. FintechOS Studio
The object properties control was not showing in the formula argument screen. FintechOS Studio
When using Formula input, the user was not able to define a text type input.

FintechOS Studio

When the user logs out, on the event from the browser window.beforeunload two endpoints were not called. The ajax call for that event is not guaranteed, therefore, it did or it did not call successfully outside of the platform control.

FintechOS Studio

The tokens taken from the address during the OCR process were broken down into the wrong fields.

FintechOS Studio

The system validated the extension records against the business unit that was found on the child instead of the organization level.

FintechOS Studio

The name of a Business Unit record cannot be changed. An error message appeared when the system tried to update the records.

FintechOS Studio

Studio menus were visible to users with User Management role.

FintechOS Studio

Double-clicking on the Next/Previous button on a wizard mode digital journey skipped a step.

FintechOS Studio

A error was generated when exporting a package that was already imported into the Studio.

FintechOS Studio

The user could not un-map an input using Formula Engine.

FintechOS Studio

When selecting the formula mapping, the formula was displayed more than once when a single mapping was created for an entity.

FintechOS Studio

Temporary blocked users were not allowed to reset their passwords after the temporary block time interval had passed.

FintechOS Studio

Unable to insert a new endpoint.

FintechOS Studio

Adding custom icons in /custom/customAssets/icons/customIconSet (attached file) returned an error.

FintechOS Studio

The release addresses several security issues in the FintechOS environment.

FintechOS Studio

With Active Directory Authentication, new auto-created users could not log in as their accounts were not created in the system.

FintechOS Studio

Related Virtual attributes were not localized.

FintechOS Studio

Fetch based grids with attribute aliases could not be saved when the allow edit option was enabled.

FintechOS Studio

spCreateEntity did not add the IsPrimaryKey argument to spCreateAttribute when creating the primary key attribute.

FintechOS Studio

Known Issues

Summary Module
Plugin assemblies must be copied and pasted in the PortalPluginStore\AddIns folder after import in FintechOS Studio in order to be functional. FintechOS Studio
The Save Changes prompt does not appear when the Insert button is clicked. FintechOS Studio and FintechOS Portal
Inline editing in views doesn’t work if the view columns are created with attribute aliases from the fetch. FintechOS Portal