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.
...
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
When importing an autogiro file and order can't be matched in the system a task is created to make back-office administrators aware that it has happened and can start the investigation. The payment is deposited in the exception account.
...
Terminated users
Terminated users are now only visible under Disabled users and they also get a status on the overview saying the user is Terminated.
...
TIN and country code TIN
...
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 reporting reports (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.
...
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.
...
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
When importing an autogiro file and order can't be matched in the system a task is created to make back-office administrators aware that it has happened and can start the investigation. The payment is deposited in the exception account.
...
Terminated users
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
...
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 latterThe 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
...