December 14th, 2020
This release introduces major improvements to the FintechOS platform's capabilities. Among others, you will be able to use drag-and-drop in the UI Designer, search from the FintechOS Portal and FintechOS Studio main menu, as well as to clone Form Driven Flows or action steps. Continue reading for the full list of improvements and fixes.
This release does not include features and fixes added to the 20.2 stream after release 20.2.6.
Search bar in the Menu
FintechOS Portal and FintechOS Studio now include search a bar that allows you to search for menu items, not the records inserted. For more details, see Overview.
Clone a Form Driven Flow
You can now duplicate a Form Driven Flow. The duplicate will have all the configurations and characteristics of the original, the only difference being name. After cloning, you can 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 the pre-existing from on the General page, then click the "Clone form" button. 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, adding an action step triggers 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:
- Processor. For more information, see Custom Processor Step.
- Action. For more information, see Action Step.
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 form Actions that will automatically 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, inserting a condition that calculates the eligibility of a potential client in the After Save grid. For more details, see Adding and Configuring Steps.
The UI Designer capability of FintechOS Platform benefits from several new features. New buttons were added in the UI Designer, which can make the following calls:
Custom Processor (and endpoints)
For example, adding a button to call the eSign processor and have it be triggered when the client clicks on button that reads "Sign agreement". For more details, see STEP 4. Working with Buttons.
Furthermore, the following can now also be found in UI Designer:
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 of a "Agree to data processing by third-party partner" statement.
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
This can be applied in an argument data of a complex type, with properties A,B, and C of type string, and D and 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.
Data Config Deployment
To achieve an import, a package can be an XML placed inside a ZIP archive, and then imported. It is available from the interface of the FintechOS Platform, or through the Package Deployer.
E-sign with tags, 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 or insurance company, it is possible to sign it by placing a tag, with coordinates, or both on a PDF file, by creating a request. The SigntureCoordinates object contains: FileName, PageNumber, and coordinates X and Y, allowing easy identification of signature via coordinates.
Business Workflow transition message
A FintechOS user is able to write a message to be displayed when a transition from a status to another is performed, so that the user on the FintechOS Portal can read it and be notified of the change. For example, the user can set the "Your application has been approved" message to be displayed in the UI, so that it is 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.
|FSD-5966||A user needed permission to read from customAction entity.||FintechOS PlatformFintechOS Portal|
|FSD-5000||This release addresses a security issue in the FintechOS environment.||FintechOS Portal|
|N/A||Access to the name of the report on the header of each simple grid report was denied.||FintechOS Portal|
|FSD-6146||In processor step on a Form Driven Flow or Digital Journey, it was not possible in General tab of the processor step to set the ''Fail Navigation Step'' to the same processor step.||FintechOS Platform|
|FSD-2148||HTML attribute that was read-only could be altered.||FintechOS Platform|
|FSD-4876||The Business workflow design diagram showed the name of the status, not the label of it.||FintechOS PortalFintechOS Platform|
|FSD-1767||In a view which had a where condition on it and was used on a form, and the main entity in the fetch did not have the character "a" as alias, the system generated an error.||FintechOS Platform|
During the OCR process done with Computer Vision on a device with Andriod 11, the screen freezes after the photo is taken on screens smaller than 6 inches.
As a workaround, if the user scrolls on the screen so that the address bar is no longer visible, then the bug does not reproduce and they can advance to the next step.
In addition, use the following code snippet to eliminate the issue:
|FintechOS Studio and FintechOS Portal|
|Plugin assemblies must be copied and pasted in the
|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|