Developer release notes Q1 / 2025

Comprehensive audit records is a core feature of the FA Platform. We store a full version history of all core data types – along with many non-core data types – allowing you to see an object's values at any point in time, and identify who changed them. Previously, this information was accessible only via the query API. Now, we introduced standard context queries for fetching audit records and historical versions of the core data types: contacts, portfolios, securities, transactions, and trade orders. Here is a simple example query that fetches the full version history of a specific transaction, and shows changes in its amount, unit price, and trade amount over time:

query{
   transaction(id:1022613){
      auditRecords{
        userName
        revisionDate
        values{
            amount
            unitPrice
            tradeAmount
         }
      }
   }
}

You can request a specific AuditRecord for a given point in time, or a list of AuditRecords based on an optional start and end date/time, for the core data types mentioned eralier. The AuditRecord provides information about when the object was saved, who saved it, and with what values.

You can query the previous version of the object in a similar way as you could for a live object, and fetch specific values of that object at that point in time. For example, you can check what values a transaction had a week ago. Additionally, you can extend your query to retrieve previous values of linked objects.

For instance, you might start by querying a past version of a transaction and then retrieve the corresponding version of its parent portfolio. In this case, the returned portfolio object represents the portfolio's state at the time the transaction version was saved. Querying previous versions of linked objects like this only works for audited data types, and may be slow. So we generally recommend avoiding highly nested queries when using AuditRecords to ensure optimal performance.

Decision tables are a powerful tool when building workflows and automating tasks. Previously, managing decision tables was possible via FA Back. Now, you can manage decision tables automatically through the new uploadDecisionTable and reloadRules endpoints. The uploadDecisionTable endpoint allows you to upload a decision table to FA Platform. By default, it also compiles and starts the rules, and gives you feedback in case your decision table is faulty. Using these endpoints requires the user to have the CONFIG.RULES permission. Listing and downloading current decision tables can be done with the general “documents” endpoint.

We introduced new endpoints for working with default tax rates. You can list default tax rates with the defaultTaxRates endpoint:

query {
    defaultTaxRates {
        portfolioType {
            code
        }
        taxCountry {
            code
        }
        taxRate
        taxType {
            name
        }
    }
}

You can import default tax rates with the importDefaultTaxRates endpoint:

mutation {
    importDefaultTaxRates(defaultTaxRates: {
        fields: [{
                field: DTR_SECURITY_COUNTRY,
                value: "FI"
            },
            {
                field: DTR_TRANSACTION_TYPE,
                value: "DIV"
            },
            {
                field: DTR_JURIDICAL_FORM,
                value: "PE"
            },
            {
                field: DTR_TAX_TYPE,
                value: "WHT"
            },
            {
                field: DTR_TAX_RATE,
                value: "25.5"
            }
        ]
    })
}

We extended the liquidity forecasting API with a option to generate a long-term liquidity forecast that include incoming cashflows from coupons and expirations until maturity. The cashflows are calculated based on the bond information in the Security window, Extra info tab.

Previously liquidity forecasting was only able to project cashflows from corporate actions which are saved in the system. Now, liquidity forecasting is also able to forecast cashflows caused by coupons and maturities of bonds, even if the corporate actions haven't been created yet.

The API returns the results grouped per account and currency. The option is turned on with includeNotCreatedCorporateActions:true.