FA Front 3.8 - Release notes

Optimization for exporting FA Front pages with your browser's printing functionality

New columns in Analytics+ and for trade orders introduced in FA Back 3.8 are also available to be used in FA Front.

Improvements done for managing profiles in FA Back 3.8 are also taken into account in FA Front - custom fields for contacts, portfolios and securities are available as selectable columns in FA Front even if a profile is defined with Vaadin design syntax, and the layouts you define in FA Front's Custom design gadget are properly visible and editable also through FA Back's Profile definition Preferences.

In addition, FA Front has been restructured in the background for it to better fit our microservice architecture. For example, certain technologies have been upgraded to latest versions, and new facilities have been introduced for improved logging.

Trade order listings in the table component now show translations in Norwegian for all values you can translate, such as transaction type or trade order status. This issue was introduced in FA 3.8 with the new trade order field "execution method" missing default translations in Norwegian - this new field now contains default translations in trade order listings also in Norwegian.

Custom design component now works correctly without an error also when the linked contact of the user has Norwegian as their language and Front is configured to use language from user's linked contact.

Mouseover text shown when hovering your mouse over the "Change roles" in the navigation, available when the logged in user has more than one role, now shows up with proper texts also in Norwegian ("Din nåværende rolle").

This version of FA Front is compatible with FA Back 3.8.4, ensuring that all fixes done to that version are also taken into account in FA Front when applicable. For example, custom fields for contacts, portfolios and securities are now correctly shown as columns on the search views in FA Back and tables in FA Front even when the profile has been defined in the "old way" of indicating in the code of the profile where the profile should be shown (e.g. fields in profiles starting with "security." are shown in the security listings). This ensures the backwards-compatibility of custom fields that have been defined before the improvements in FA 3.8.

This version of FA Front is compatible with FA Back 3.8.5, ensuring that all fixes done to that version are also taken into account in FA Front when applicable. For example, optimizations in memory usage of Analytics+ when analytics is run with a time series based on frequency has an effect on loading data in Analytics visualization component if the component is configured to use the "Frequency" parameter.

Transaction listings in FA Front no longer include transactions that have been marked as "hidden".

This version of FA Front is compatible with FA Back 3.8.9, ensuring that all fixes done to that version are also taken into account in FA Front when applicable. For example, changes in Analytics+ are applied also in Analytics and Analytics visualization components in FA Front.

Fixed an issue that prevented FA Front to start up due to a missing dependency.

This version of FA Front is compatible with FA Back 3.8.10, ensuring that all fixes done to that version are also taken into account in FA Front when applicable. For example, fixes in Analytics+ are taken into account also in Analytics and Analytics visualization components.