FintechOS 20.2.6

December 21st, 2020

This release focuses on the configurations and security of the FTOSApiSMS provider, and also fixes various issues from previous releases.

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

Configure the FTOSApiSMS provider

The FTOSApiSMS provider is now at your disposal. It enables the sending of messages, such as the message for a campaign, for notifying a client, or the SMS-based Two-Factor Authentication. After the proper configuration is done in the web.config file, use the Omnichannel Communication Automation to add the provider in the list of available channels. For details, see Configure the SMS provider.

There are two possible providers for SMS:

  • GatewaySmsOTP - which will populate a table in the DB called EbsMetadata.FTOS_DPA_MessageQueue
  • FtosApiSms - which will send the text message to the specified phone number.

For the SMS-based Two-Factor Authentication, in the web.config file, set the ChannelProvider property to "FTOSApiSms" in order to use this specific SMS provider. This feature enables a though security validation for your users through the FTOSApiSMS. Hence, the system is protected and so are your users when logging in. For details, see Configure Multi-Factor Authentication to use an SMS Service provider.

Customizing the text for messages sent through SMS on Multi-Factor Authentication process

A new server side method was implemented to support the sending of SMS. It is friendly to use, allowing you to add the phone number, the body of the message, the name of the sender, and the aforementioned SMS provider, with the following syntax:

Copy
function server.messaging.sendSMS(phoneNumber: string, message: string, {from: string, provider: "GatewaySmsOTP"|"FtosApiSms"}): void

  

For details, see server.messaging.sendSMS.

Fixed Issues

No.

Summary Module

N/A

After the creation of a data config package and adding new records from the master entity to it, followed by adding records to the master entity, the refresh button did not work to add the records to the grid.

FintechOS

N/A

A package with two Form Driven Flows added to the same Digital Journey and a rule on the first Form Driven Flow to navigate to the second flow did not import to the targeted environment the rule of navigation.

FintechOS

N/A

On the source environment, the entities to be exported had constrains. On the targeted environment, these entities lacked the constrains. When deploying the package, after the moment of import, no error was displayed and the package was not imported.

FintechOS

FSD-6270

A user could name the attributes using the same name of a system attribute.

FintechOS

N/A

No error message was displayed when disabling a Unique Constraint from an entity thought it was used in the Data Import Template or Configuration Data Definitions.

FintechOS

N/A

Virtual Attributes from extended model of an entity could be deleted even if they were configured to be used on a field option of a Form Driven Flow.

FintechOS

N/A

Exporting or importing Primary Key details after they have been modified did not successfully export/ import the details updated.

FintechOS

N/A

For the following entities FTOS_CALC_Formula, FTOS_CALC_DataMapping, FTOS_DPA_MESSAGEQUEUE, FTOS_DPA_MESSAGESTATUS, FTOS_DPA_COMMUNICATIONCHANNEL, FTOS_DPA_CHANNELPROVIDER, FTOS_DPA_CHANNELPROVIDERSTATUS, SYSTEMUSER, SECURITYROLE, BUSINESSUNIT, ENTITY, ATTRIBUTE, ENTITYFORM, ENTITYVIEW, DATAIMPORT, DATAIMPORTITEM, FEED, OPTIONSET, OPTIONSETITEM, APPLICATIONLANGUAGE, CHART, DASHBOARD, FINCHART, RELATIONSHIP, REPORT, BWRule, scheduleTrigger ,BW, BWStatus, it was needed to create a unique constraint to export the data and the user needed rights to create relationships.

FintechOS

FSD-2682

To archive a file using addToArchive(), in the file upload white list there was no .zip or .rar extension available.

FintechOS

N/A

For XML package that included the order Index, it imported it as a numerical column generated then automatically.

FintechOS

N/A

A customAction with isSystem=1 was not updated when importing it using deployment package.

FintechOS

N/A

When the user imported a package with an entity that was new on the environment and the primary attribute name had the length changed from 100 (default) to another value, the field imported had the default value.

FintechOS

N/A

When importing an entity with a unique constrain to the targeted environment, the Include Business Status and Mirror Collection were not exported as mentioned in the data config definition.

FintechOS

N/A

When deploying a package with an entity, business workflow and business workflow configuration with a business transition, an Action Group, with an item on Action Before/ Action After, the EntityBWTransitionAction was inserted as new item instead of an update, on import.

FintechOS

N/A

The httpPost/callPostMethod did not support a content-type other than "application/json".

FintechOS

N/A

Loading information from external data source could not be bigger than 100 character due to a limitation of the temporary table created by the system.

FintechOS

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

In a Form Driven Flow, the relation between Step and Processor Type is made through ID not name.

FintechOS