Skip to main content

Developer release notes Q2 / 2025

The Q2 2025 release features new analytics metrics, as well as jsreport improvements.

New standardized Analytics+ columns

The following Analytics+ columns are now part of our core offering. Previously, some of these fields were provided to some of our customers through custom Analytics+ columns. Such custom columns may now be removed, in favor of the new standard columns. The following new columns are related to private equity investments:

  • commitmentTotalSec

  • committedCapitalSec

  • distributedCapital

  • distributedCapitalSec

  • distributionsSec

  • dpiSec

  • grossPaidInCapital

  • grossPaidInCapitalSec

  • marketValueSec

  • paidInCapitalSec

  • percentageDrawnCapital

  • percentageDrawnCapitalSec

  • picSec

  • recallableDistributions

  • recallableDistributionsSec

  • remainingCommitmentSec

  • totalValueSec

  • tvpiSec

  • rvpiSec

We also added the following non-private-equity-related columns:

  • openPurchasedAccruedInterest

  • openSoldAccruedInterest

  • realizedPaidInterest

  • marketValueSec

  • purchasedAccruedInterest

Jsreport improvements

We implemented several improvements to the FA Platform’s embedded Jsreport service. You can read more about the changes in the Technical release notes Q2 / 2025. If you are a current jsreport user, you will automatically receive access rights to jsreport through Keycloak. Use thethe Login with OAuth server button to log in, instead of providing a username and password. Migrating jsreport files from the file system to a blobstore is handled by us automatically as a part of the version upgrade, and should not impact jsreport users.

Additionally, we introduced a new reporting parameter “contactDbId” that is available for both Jasperreports and jsreports, whenever a report is run per contact, or when a single report is run against a contact selection. The parameter is not provided when running reports per portfolio, or as a single report against a portfolio or group. Previously, including contact information in a report required fetching the contact based on e.g. the given portfolio’s primary contact. However, that approach may produce an incorrect result, when portfolios are linked to multiple contacts.

Other improvements

  • We restricted certain technical endpoints that were previously available for environment monitoring purposes, to only be accessible to internal network requests.

  • We fixed an issue where data-changes events were being produced before profile information was persisted when saving contacts, portfolios or securities in FA Back.

  • We fixed an issue where representative tags had unnecessary leading and trailing commas.

  • We removed the latestPortfolioReport query from the portfolio context, because it was not intended to be used via API.

  • The importLimitedTradeOrder API now supports tag-only updates for trade orders in all statuses. Previously, it was possible to modify or cancel orders from FA Client Portal, but only if the order status was “Open”. Cancellation workflows – triggered by assigning the “apitradeorder–Request cancel” tag – can now be applied to orders in any status, including those already sent to market. The API detects when only tags are being updated and bypasses the previous restriction.

In this section: