Skip to main content

Developer release notes Q2 / 2022

From the Q2/2022 version onward, each of our releases will be accompanied by technical release notes. Technical release notes are primarily intended for users who have built or intend to build extensions to or integrations with the FA platform. These technical release notes highlight new opportunities for extension/customization, as well as potential backwards compatibility issues with our new releases.

Integrations section to FA Developer

The Integrations section of FA Developer allows you to conveniently build and administer customized integrations between the FA Platform and other systems. For more information, please refer to the FA Developer application release notes.

New features for custom process developers

During the Q2/2022 version, we built various tools that you can use when building custom processes via the FA Developer application. For more information, please refer to the Processes section of FA Developer guide.

Improvements and changes to GraphQL APIs

  • We can now whitelist external domains, and allow browsers in those domains to call our GraphQL APIs without encountering CORS errors.

  • Our recommended way to authenticate GraphQL API requests is through a new Keycloak client “external-api” combined with either a technical user or a real user - depending on the case. Please refer to the API Integrations section of FA Developer guide for more information.

  • We introduced a new GraphQL API for generating jsreport reports.

  • We introduced new GraphQL APIs for importing a transaction or trade order, which can be used by limited and extended limited visibility users.

  • We now support requesting information about a portfolio’s portfolio groups as part of your GraphQL requests.

  • Imports via GraphQL APIs now run rules by default. Previously we defaulted to not running rules, which was inconsistent with all other types of imports that we do. If you need to run imports without running rules, you now need to provide the withRules = false parameter.

  • We optimized how our analytics APIs work when run against a single date. As a side-effect, certain figures regarding changes since the previous day are no longer available in single-day analytics. In the unlikely situation that such change figures are needed even for a single-day report, the analysis may be changed to a two-day analysis instead.

  • We removed the "portfolioReport" and "portfolioReportSubItems" endpoints; such data should instead be loaded as a subquery for returned portfolios.

  • We restricted limited and extended limited visibility users from performing certain types of GraphQL API calls, to apply the limited and extended limited visibility concept consistently across the platform.

Option to run dedicated API instance

We now have the option to reserve dedicated resources for the APIs provided by FA Back. This includes both GraphQL and REST APIs. In some cases this provides APIs with higher availability and more consistent response times. We will roll out this feature to those of our customers who we evaluate to benefit from it - namely those who use our APIs in a particularly time-critical / business critical manner.

Miscellaneous

  • We have a service bus topic called “report-calculation-events” that you can connect to if you want to be notified of, or otherwise react to, completed report calculation events. This topic now includes completed purchase lot (report sub item) calculations in addition to full calculations and calculations of daily positions.

  • We fixed a bug concerning the IDs that are passed to reports, when running them from the transaction and trade order screens with “per customer” or “per portfolio” grouping.

  • We fixed a bug when importing transactions or trade orders with “AUTO” account: the importer no longer incorrectly prefers a non-cash account of a matching currency over the default (cash) account of a non-matching currency.

  • We fixed a bug where single-day reports would incorrectly be provided both a start date and end date parameter in certain situations. Now only the end date is provided.

  • We fixed a bug where report packages in some client environments were limited to just a small handful of reports. Now you can include as many reports as you like in a report package.

In this section: