Skip to main content

FA Front 3.13 - Release notes

FA Front 3.13 [latest updated version FA Front 3.13.3] has been released.

FA Front 3.13

Contains : Improvements in translating FA Front pages

Released: January 18th, 2022

Improvements – see attached FA Front 3.13 Release notes for more details:

FA Front 3.13 Release notes.pdf

  • Support for translating FA Front to different languages and overriding texts directly in FA Front

In addition to the improvements highlighted in the release notes, FA Front 3.13.0 includes the following fixes and improvements:

  • If something goes wrong in FA Front and there is an error, regular end-users will no longer see the non-descriptive error message with purple text on white background, which didn't disappear before the user logged out. If an error occurs when an ADMIN user is logged in, the error message is shown in a separate popup, allowing the user to take note of the error and get rid of it by closing the window.

  • When you generate a report in FA Front through the report component, the report will now get the same parameters as the report would get in FA Back, ensuring that reports look the same regardless of where they are generated from.

  • Custom content component now works correctly even if you have two contacts or portfolios in the background with the same external IDs.

  • Custom content component now works correctly also when the custom content is fetched with GraphQL queries and you have either selected a contact with no portfolios or you have selected a contact with "All portfolios" selected.

  • You can now create a new design in Custom design or Datagrid component's configurations even if you have first selected to view one of the existing designs.

  • FA Front now properly reacts when you update extensions, such as processes or decision tables, through FA Back – changes now take effect directly, without having to restart FA Front.

  • In addition, log4j has been upgraded to the latest version of the library. This upgrade includes a fix to a recent serious security vulnerability.

Updates to FA Front 3.13

FA Front 3.13.1 Release notes

FA Front 3.13.1 is an update to FA Front 3.13. This update includes the following fixes:

  • Fixed an issue related to FA Front user interface opening up as empty if Scandinavian letters were used within some of the texts on the user interface. This issue appeared after upgrading certain underlying technologies, which had the unwanted side effect of changing our internal APIs to use ISO-8859-1 encoding instead of UTF-8. This issue is now fixed, and Scandinavian letters appear normally.

In addition, this version contains all fixes from version FA 3.12.1:

  • Fixed an issue in Analytics visualization component related the component showing its data for a wrong time period when you don't have a time period selector in the toolbar and have configured the component in a specific way in an attempt to show data from the beginning of portfolios' history.

FA Front 3.13.2 Release notes

FA Front 3.13.2 is an update to FA Front 3.13. This update includes the following fixes:

  • Fixed an issue related to dates showing with a technical format (a long number representing seconds) in FA Front's user interface. This issue appeared after upgrading certain underlying technologies, which had the unwanted side effect of changing our internal APIs to use different date formatting. This issue is now fixed, and dates appear normally.

  • Filtering a security listing in the table component now correctly returns your securities when you pre-filter the list with multiple tags.

FA Front 3.13.3 Release notes

FA Front 3.13.3 is an update to FA Front 3.13. This update includes the following fixes:

  • Custom content component now works correctly also when the custom content is fetched with GraphQL queries and you have either selected a contact with no portfolios or you have selected a contact with "All portfolios" selected. This was intended to be fixed already in FA Front 3.13, but was mistakenly excluded from the release.

  • FA Front now correctly uses the date formats defined in FA Front throughout the application, also in generating a report and showing data in a table. Before, some places were using format configurations from FA Back, resulting in mismatches if formats had been updated in FA Front.