Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These release notes contain new features, improvements, and fixed issues in releases 2.38

Planned release Release date: 2021-12-06

New Features and Improvements

...

Mass management of manual orders

We now have the possibility to You can now select several orders and mass manage them in bulk. This means that you can select serval orders and fill and settle them at the same timemultiple orders at once, saving considerable time compared with handling these individually. Read more here.

...

Tax Identification Numbers (TIN)

It is now possible to add TIN and country code in Bricknode Broker. These new fields are found under the Detail tab on a user record. The properties are needed in the tax reports (new from tax period 2020) and have only been in the Tax application for the customers to add manually. Learn more: Tax Identification Numbers (TIN) and Release 1.11 - Tax Reporting Application

...

Performance improvements in the system

We have improved the performance when filling and settling internal and manual resulting orders and also when batching (netting) internal orders. This operation has been time-consuming and will now work much faster.

The listing of external accounts took a long time in the tickets “Withdraw Money” and “Automatic Payment”. We have now made some changes so it will go faster.

We now show all currencies in the ticket “Withdraw money” instead of only SEK. We have therefore added a validation that only SEK is supported when selecting Autogiro. The performance is improved when showing all possible currencies that the customer has.

...

The search button is now disabled until the search is done or you enter a new value in any of the filter boxes. Previously the user could start a new search before the first search was finished which caused a load on the server and performance problems.

...

Only one account will be selected when navigating to a partner user in Admin. This view has been very slow since a partner can have hundreds of accounts.

...

Search with BFS-id in several lists

We made it possible to use BFS-id when searching several lists in the system. Some CSV exports only contain the BFS-id and then it is useful for the back office administrator to use the BFS-id when doing a search. It is possible to use the BFS id for example the instrument, account, and user lists.

...

Unmatched payments in Bricknode Broker

...

Terminated users are now only visible under Disabled users and they also get a status on the overview saying the user is Terminated.

...

New settings for Partner - manage deposits

We now have the same settings for partners that we have for end customers and administrators. Settings where we can allow partners to manage deposits on the partner front, like change date or amount on deposit orders that are not sent to BGC (sent active).

...

New checkbox on instruments

A new setting on instruments to exclude them from fee-related selling. This could for example be used for instruments that are traded monthly. The checkbox is only visible when having the add-on for Fee Manager activated. You will find the new setting under the section Fees on an instrument. There is also possible to filter on this in the instrument lists.

...

TIN and country code TIN

We have added properties for TIN and country code TIN in Bricknode Broker. These new properties are found under the Detail tab on a user. The properties are needed in the tax reporting (new from tax period 2020) and have only been in the Tax application before for the customers to add it manually. More info is coming soon.

...

Performance improvements in the GUI

...

We now show all currencies in the ticket “Withdraw money” instead of only SEK. We have therefore added a validation that only SEK is supported when selecting Autogiro. The performance is improved when showing all possible currencies that the customer has.

The search button is now disabled until the search is done or you enter a new value in any of the filter boxes. Previously the user could start a new search before the first search was finished which caused a load on the server and performance problems.

Partner

We have made performance improvements on the account overview for partners.

Trade time for internal orders with manual resulting order route

The trade time was set to Now on internal orders but the default behavior should be the same trade time as the resulting order. When filling the resulting order the internal orders should get the same trade time. The date can always be changed in the GUI.

New settings for Partner

More info soon.

...

Possibility to cancel several orders

We added the possibility to cancel several individual orders, we have only had this possibility in some order lists like subscription orders.


Price check when filling manual order

We have added a check when filling a manual order that the price difference that is set on the execution interface setting (System Data > Execution interface) is not too big. This will prevent the user from entering the wrong price.

...

Disabled back button in the web browser

The back office administrator could by mistake click on the back button in the browser and would be moved to the login page and lose the open tabs/work in the system.

...

API - 2.38

This release involves changes in the API, make sure to inform your external developers and update your service reference. Please read our changelog to get all the information about which API-methods that are affected.
There is a breaking change in the method CreateReservations. We have removed the property Order which carries the same information as Reference. The user should henceforth only use the latter.The upcoming API has been uploaded to a test environment, so your developers can update the "service reference" and make any necessary changes before the actual update.

A release of our NuGet package is also available:

...

NuGet Gallery | Bricknode.Soap.Sdk 6.3.0

There is a breaking change in the method CreateReservations.

Manage fees and delete custom fields via API

We have four new methods for creating managing fee records and a new method for deleting custom fields which are needed to be able to delete fee instructions. This method can also be used for deleting custom fields on other entitiesany entity, like accounts.


Data type Enum is enabled as Args input in the API

...