Skip to main content

Technical release notes Q4 / 2024

Technical release notes highlight the development work done to make the FA Platform fast, secure, reliable, and adaptable.

Performance

FA Back transaction and trade order search performance

Why?

In some cases, searching for transactions and trade orders with tags in FA Back suffered from poor performance.

Who is this for?

This is for FA Back users who work with tag-based transaction and trade order searches or dashboards.

Details

Despite significantly improving the performance of many kinds of searches in our 2023 Q2 release, we received reports of certain tag-based transaction and trade order searches continuing to take an inconsistent, and occasionally excessive, amount of time.

The issue was caused by inconsistent and poor performance of the indexing that we use for tag-based transaction and trade order searches. Using tag-based indexing also prevents the use of other more effective indices for searching.

We resolved the issue by adjusting our tag-based searches to prioritize certain other indices over the tag index. This enhancement doesn’t make tag-based searching for transactions and trade orders faster. However, it does improve the speed of searching for transactions and trade orders based on a specific status, transaction date range, or certain other criteria in combination with a tag. 

FA Client Portal performance

Why?

Our goal is to ensure FA Client Portal users enjoy minimal loading times and exceptional responsiveness.

Who is this for?

This is for FA Client Portal users.

Details

By eliminating unused fields queried during user login, we successfully reduced the initial loading time, enhancing the overall user experience.

FA Fund Management performance

Why?

We wanted the NAV status view to load faster, even with a large number of funds under management.

Who is this for?

This is for FA Fund Management users.

Details

Various technical optimizations allowed us to significantly improve the loading speed of the NAV status view without impacting the functionality of the view itself.

Extension performance

Why?

We found ways to improve the performance of Norwegian tax reporting and our periodic relative fee formula.

Who is this for?

This is for users of Norwegian tax reporting and the periodic relative fee formula.

Details

The periodic relative fee formula is now much faster at loading daily positions which are the basis of the calculation.

We optimized Norwegian tax reporting to make it run faster and added a background generation option. Users can now continue working in FA Back while the tax reports are generated in the background.

Reliability

Improved fault tolerance in FA Back and FA Fund Management

Why?

We wanted extra safeguards to guarantee that transaction, purchase lot, and position data remain in sync even in case of unexpected problems.

Who is this for?

This is for FA Back and FA Fund Management users.

Details

In the 2024 Q1 release, we introduced a layer of redundancy to ensure that mass-saving transactions in FA Back automatically triggers purchase lot and position updates even in case of unexpected problems such as a server restart or connection issue. This mechanism works well, so we incorporated it in the Transaction window, Contract window, and contract import in FA Back and in the FA Fund Management application.

Improved memory management for large application instances

Why?

We found a more efficient way to allocate resources within our largest application instances.

Who is this for?

This is for FA Back users in environments with large resource allocations.

Details

The amount of resources that FA Back requires depends on the usage, and may vary greatly. Memory is particularly crucial: if the application runs out of a specific type of memory, it may be forced to restart. We were able to effectively increase the amount of memory available to some of our largest application instances by optimizing the percentage of memory allocated to heap vs. non-heap, which will improves the resilience of those applications under peak load.

Push notifications

Why?

We want to keep you informed about important events within the FA Platform.

Who is this for?

This improvement is for all users of the FA Platform. Push notifications are initially only sent to users of a limited set of features, but notification coverage will be expanded during 2025.

Details

Push notifications are a powerful feature that allows us to notify users of things that require their attention, especially in response to activities that happen in the background. We are rolling this feature out gradually, starting with the 2024 Q4 release. Initially, we only produce events for a limited set of features: fund management and process monitoring. 

Except for FA Client Portal, all FA Platform users can now see a bell icon in the Global app bar on the left. Users of FA Fund Management and process monitoring can view notifications from the last 30 days by clicking the new icon. FA Fund Management users get notifications about NAV-related tasks they initiate. For process monitoring, notifications inform users when a process fails.

We will extend notifications to a broader set of features in the future. Push notifications improve the usability of many features, especially ones involving background processing.

Security

This release introduces several security enhancements. Although these enhancements are likely to go unnoticed by FA Platform users, they are worth mentioning because they represent the significant investments that we make on a continuous basis to keep the platform secure. 

Specifically, in the Q4 release, we reviewed the permissions of our various services, started applying certain security headers to all HTTP requests, and future-proofed the authentication logic in FA Back and FA Front. We also improved session management in FA Back.

Trading integrations

Our trading integrations were extended with several new capabilities in the Q4 release:

  • Our trading integration to Allfunds now supports reading cost and charges from the ComssnGnlDtls block, alongside the original ChrgGnlDtls. Additionally, we improved our ability to capture rejection reasons from the XtndedRsn block when no reason is provided in the AddtlInf field.

  • We now support sending subscription orders in units for the ISO20022v3 format. Previously, only amount-based subscription orders were allowed.

  • The FA Platform supports several new message types for the ISO20022v4 format:

    • Incoming messages:

      • setr.013.001.04 (SwitchOrderV04)

      • setr.014.001.04 (SwitchOrderCancellationRequestV04)

      • setr.011.001.04 (SubscriptionOrderCancellationRequestV04)

      • setr.005.001.04 (RedemptionOrderCancellationRequestV04)

    • Outgoing messages:

      • setr.015.001.04 (SwitchOrderConfirmationV04)

      • setr.017.001.04 (OrderCancellationStatusReportV04)

    • Switch orders are recorded in FA as two separate trade orders (sell leg and buy leg).

Miscellaneous

We upgraded our JSReport version to 4.6.0 and now bundle it with the @jsreport/jsreport-unoconv library (see https://jsreport.net/learn/unoconv). This library allows you to work with OpenOffice/LibreOffice supported formats.