FintechOS Platform 20.1.2

This release introduces new Digital Developer tools, such as methods for the Client and Server SDK, new configurations for the Digital Experience Portal, security and dashboard improvements, and fixes various issues from previous releases. Continue reading for more information.

What's New

Digital Developers Tools

DB Task

For high-performance computing, this release introduces the DB Task feature, enabling you to execute SQL stored procedures which perform massive data computing.

Using DB Tasks, you can only execute stored procedures under the 'Ebs' DB schema.

If your business case requires that the DB tasks are executed only by designated roles within your organization, you can specify which security roles can execute the DB Task.

For information on how to add a DB Task and how to execute it, see the Fintech OS Studio User Guide.

New Client SDK Method

This release introduces a new Client SDK method, ebs.goToDashboard , which navigates to the home page and selects the provided dashboard. For more information, see the Client SDK Reference Guide, section ebs.goToDashboard.

New Server SDK Method

This release introduces a new Server SDK method, getTabularDataFromFile, which enables you to process a file from a known folder into a TabularData structure.


getTabularDataFromFile(filename: string, options?: IWorkflowTabularDataOptions): IWorkflowTabularData
Parameter Type Description
<filename> string The path of the file in a known folder. ex: Import/test1.csv
options object: IWorkflowTabularDataOptions Optional settings that can be given to the method:
  • encoding (string): the encoding of the file (defaults to UTF-8)
  • delimiters (string[]): list of delimiters used in the file (default to [","] for CSV files)


The method returns an instance of WorkflowTabularData that implements the IWorkflowTabularData.

Definition of IWorkflowTabularData

interface IWorkflowTabularData {
        getRow(index: number): IWorkflowTabularDataRow;
        getAllRows(): IWorkflowTabularDataRow[];
        saveToTemporaryTable(tableName: string, options?: IWorkflowImportToTemporaryTableOptions): void;
        rowCount: number;


  • getRow(index: number): IWorkflowTabularDataRow: returns the row that is placed at index. ex: tabData.getRow(5)
  • getAllRows(): IWorkflowTabularDataRow[]: returns the list of rows. ex: tabData.getAllRows()
  • rowCount: number: gets the count of rows.
IWorkflowTabularData.saveToTemporaryTable(tableName: string, options?: IWorkflowImportToTemporaryTableOptions): void;


  • tablename (string): the name of the temporary table that will be created (without "#"). ex: test_import
  • options (object: IWorkflowImportToTemporaryTableOptions): optional setting that can be given to the method
  • skip (number): the number of rows that can be skipped from the start of the table. ex: tabData.saveToTemporaryTable("test_import", { skip: 3 })
  • hasHeader (string): if true then the first row of TabularData will be used as the column names for the generated table

The temporary table is autocratically created if it does not already exist. The structure of the table is created by determining the maximum count of columns from the TabularData's rows and creating enough columns to fit all the data.

All columns are created the same as the Text attribute. The column names is determined by looking at the provided headers first, if the data at the current column exists and it is a valid column name, then it is used as the column name, otherwise the column name is computed as c{index} (ex: the 5th column will be named c5).

Definition of IWorkflowTabularDataRow

interface IWorkflowTabularDataRow {
        getColumn(index: number): string;
        getAllColumns(): string[];
        columnCount: number;
  • getColumn(index: number): string: returns the column that is placed at index. ex: tabDataRow.getColumn(5)
  • getAllColumns(): string[]: returns the list of columns. ex: tabDataRow.getColumns()
  • columnCount: number: gets the count of columns

Digital Experience Portal

Portal configuration options available in the web.config file

This release introduces extensive options to configure various parameters (UI elements) of the Digital Experience Portal directly in the web.config file:

  • Use stripped theme with minimal CSS elements
  • Load custom style sheets
  • Configure the footer text per language
  • Move language selection to the user profile panel
  • Hide Select Theme and Select Palette settings
  • Hide company Logo
  • Hide the Main Menu
  • Hide search in the Main Menu
  • Hide APPS dashboard
  • Hide My Profile Link from the User Profile panel

For more information, see Configure Digital Experience Portal.

Portal Profiles

This release introduces a new feature, Portal Profiles which allows you to have specific customization per portal.

Using portal profiles, you are able to:

  • choose company logo
  • choose background and login background images
  • set specific system parameters
  • attach menu items on portal profile
  • add dashboards on portal profile

To customize digital experience portals using a specific portal profile you need to create the portal profile, then configure FintechOS Platform to use that portal profile.

For more information, see the FintechOS Platform User Guide, section Using Portal Profiles.

Navigation back to a dashboard

With this release, when a user navigates from a dashboard and then clicks the Back button, the user will see the previous dashboard.


Security Roles on Endpoints

For higher security, with this release, you can choose which security roles have the privileges to call actions on endpoints. The endpoints configuration page has been improved to allow you to attach security roles on endpoints.

For backwards compatibility, the “Registered Users“ security role is automatically added to all endpoints created in previous versions of FintechOS Studio.
The “Registered Users“ security role that is automatically added to all endpoints created in previous versions of FintechOS Studio does not ensure the backwards compatibility for unauthenticated portals. In this case, you need to manually configure the security roles assignment or import it.

For more information, see the FintechOS Platform User Guide, section Creating Endpoints.

Dashboard Improvements

This release introduces two new fields which enable you to set the spacing between the dashboard's elements:

  • The Widget Vertical Spacing field allows you to set the amount of vertical space to be added between the dashboard's elements. Default value is 20. The vertical spacer automatically adjusts with the screen size your page is viewed on.
  • The Widget Horizontal Spacing field allows you to set the amount of horizontal space to be add between the dashboard's elements. Default value is 20. The horizontal spacer automatically adjusts with the screen size your page is viewed on.

For more information on how to create dashboards, see the FintechOS Platform User Guide, section Creating Dashboards.

eSign - Download Envelope Log

The forth pillar of FintechOS security, logging, provides you with comprehensive audit trail of what happened at any given time and who performed the action.

In this regard, a new option has been added to the downloadlRequest method which allows you to get the envelope log.

The envelope log file contains information about the envelope:

  • the general information
  • status of the envelope
  • the creation date
  • the recipients and the changes they made to the document, (for instance, which signature fields were placed on the document)
  • the time when the workstep was finished

For more information, see the eSign User Guide, section Electronic Signature Methods, Download Signed Document and Envelope Log.

Server SDK Documentation

The Server SDK Reference Guide is now available and provides you with a comprehensive list of JavaScript functions you can use in server automation. For each function, the guide provides you the definition, syntax, request parameters, response, and examples.

For information on how to use the FintechOS Platform Server SDK, see the Server SDK Reference Guide.

Known Issues



In the current version charts aren’t exported/imported with the deployment packages

Deployment Packages

Plugin assemblies need to be copied and pasted in the Portal PluginStore\AddIns folder after the import in FintechOS Studio in order to be functional 

FintechOS Studio

UploadEBS – The message error that is displayed when the virtual folder is missing is not clear

FintechOS Studio

General – The prompt for saving changes will not appear when the “Insert” button is clicked

FintechOS Studio & Experience Portal

Editing inline doesn’t work if the view columns are created with the attribute aliases from the fetch.

Experience Portal

The View column is displayed in editable entity views when the ShowViewButton checkbox is unchecked.

FintechOS Studio & Experience Portal

When setting a user password from myAccount or from the system users list, an error is thrown if the password contains special characters.

FintechOS Studio

Sometimes, form names that contain spaces are not URL encoded correctly when displayed in the Experience Portal.

Workaround: Avoid using form names that contain spaces.

FintechOS Studio & Experience Portal

Custom action shortcut widgets set up on the Experience Portal dashboard do not open the corresponding custom actions.

Experience Portal

Using the ebs.generateForm method with the onlyTemplate option causes an error when called from a digital journey in wizard mode.

FintechOS Studio