Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

All our recent updates - from new features to enhancements.
Currently only for Bricknode Broker in MongoDB Atlas.
Follow us on Twitter for the latest updates @BricknodeBroker and @Bricknode

August 2022

In progress

Planned release date: 2022-08-17

New Features and Improvements

API

Please read our changelog to get all the information about which API methods have been updated.
A release of our NuGet package is also available:

Fixed issues

 Added a property in BusinessTransaction.csv

We have added the property/column “IsCorrected” to the file BusinessTransaction.csv in the nightly SFTP export. (BB-576)

 Crash in development chart when sending in a time stamp in Trade Date via the API.

A problem occurred when you submitted a time stamp in Trade Date via the API. The development chart crashed when the trade date had a time value. We have now changed so a time stamp can be submitted. (BSS-9643, BB-1214)

June 2022

Release date: 2022-06-21

New Features and Improvements

MongoDB Atlas and Azure

We have changed to MongoDB Atlas which is a fully-managed cloud database and moved Bricknode Broker from AWS to Azure. All new Broker customers will be using the re-worked storage backend.

Customer values

  • Standardized backend - faster time to respond to support issues.

  • Move to modern CI/CD - shorter time to market for apps and features.

  • More monitoring and logging added - easier to troubleshoot> faster response times.

API

Please read our changelog to get all the information about which API methods have been updated.
A release of our NuGet package is also available: https://www.nuget.org/packages/Bricknode.Soap.Sdk/8.1.0

Fixed issues

 Supplier Payments (BGC) - wrong order of the rows in the exported file

The exported file from Bricknode broker was generated with the wrong order of the rows and could therefore not be imported at the bank. This is now solved.

 Better error handling in AllFunds workflow when receiving duplicate messages with execution information

The customer received duplicate messages from AllFunds with execution information. This caused the crash. We have improved the code so this exception will not happen again in the future. Instead, we’ll add an error log entry that it happened, and use one of the fund instruction executions.

  • No labels

© 2009 - 2023 Huddlestock Technologies AB All rights reserved | Huddlestock Terms of use | Support portal