Standard Solution December 2023 - Release notes
Released: January 1st, 2024
The Standard Solution December 2023 release introduces file size validation in document signing, enhanced futures mark-to-market process, and other improvements and fixes.
File size validation in document signing
Why?
We added validation to prevent cases when a document is sent for signing but no response is received from Signicat.
Who is this for?
This improvement is for anyone who uses document signing services.
Details
The Signicat service has a file size limit. If a file size exceeds this limit, Signicat doesn’t send any response. In these cases, it was difficult to identify the reason why Signicat didn’t receive the file.
Now, we included the file size check when the document is sent to Signicat. The check is performed both in the user interface and in the background task executed during scheduled runs. If the document sent to Signicat by the user exceeds 4.2MB, FA system shows an error notification. In case of a scheduled sending, an error tag is assigned to the contact if the file size is too big.
Enhanced futures mark-to-market process
Why?
This improvement was made to remove some limitations in the mark-to-market process.
Who is this for?
This improvement is for the users who have futures transactions in portfolios and track daily variation margins.
Details
In the latest version of the mark-to-market process, the following limitations are addressed:
Previously, the booking to the margin account was a result of multiple transactions that did not align with the variation margin change booked at the custodian/prime broker.
Intraday gain/loss is now captured accurately.
It is now possible to properly capture gain/loss in the posting rules for bookkeeping futures transactions.
The mark-to-market transaction has been enhanced to account for settlement lag (picked up from the future security setting).
Fixes
Trade order management
The Validate orders process now works with the TOM_VAL role as initially intended. The TOM role no longer gives access to the process.
The Bulk trade order process no longer fails if the configuration to order types to treat as unit order is missing.
The Bulk trade order process no longer fails if the configuration to carry over the unit price to bulk orders is missing.
Utilities
The description of the ROLE_SVS role is updated and can be seen in the FA Admin console, Role management view. Previously, it had an incorrect description.
Tax reporting
Fixed a class conflict issue in Norwegian tax reporting which could cause tax reports to fail randomly.
Field 049 in the VSRVERIE Finnish tax report was removed. The field is optional and not populated by the FA Platform, and therefore it could be removed.
Payments
CAMT file reader no longer invalidates files unintentionally if there is a line break (or another white space) at the end of the file.
Market data connector
Refinitiv market data feed no longer fails to fetch all securities if one or more of the requested update codes returns a missing or invalid price.
Reporting
Fixed an issue in allocation by category report which didn't run properly after the JDK 17 upgrade.
SIRA/NAV reporting now correctly separates custodian and management fees in the report.
The custodian report for Danske Bank no longer shows a confusing text when generating the report. Previously, it could show “No Data found for [fund]” even though the report was successfully generated.
Model portfolio management
The tag rebalance status process now works. Previously, it stopped working due to a deprecated Drools method.
Accounting
Standard bookkeeping CSV export no longer ignores certain search criteria when launched against a search.