mbi 2024 release
- Higher performance of the system
- The JMS module has been removed from the product without replacement. This also includes all JMS workflow tasks
- The algorithms SHA384WithECDSA, SHA512WithECDSA, SHA3-256WithECDSA, SHA3-384WithECDSA and SHA3-512WithECDSA have been added to the key generation in the certificate manager. In addition, the system finds out the name of the elliptic curve if it is an EC key. EC keys can now be generated on a named elliptic curve.
- There is a new module: "OAuth2". This can be used to implement authorisation via external authorisation servers using the OAuth2 protocol for various communication methods (e.g. HTTP, POP3, SMTP, IMAP). The OAuth2 module also supports PKCE (Proof Key for Code Exchange), so that it can also be used for OAuth 2.1, which is not yet in use as of 2024.
- Help texts have been added to the client directly in the GUI, which are marked with a question mark symbol. If you move the mouse over the question mark symbol, you will receive a help text
- In the server information, the standard file encoding of the operating system is now displayed on the server side. This is interesting because there is a "default encoding" in many places in the settings - and the user should be able to find out what this is for their OS
- The "PDF, PDF/A, ZUGFeRD, FACTUR-X, PDFSignature" module has been renamed "E-Invoicing". It now also supports the "Factur-X XRECHNUNG" subprofile for invoice processing in Germany. An example of a "Factur-X XRECHNUNG" creation with an XRechnung v2.2.0 attachment has been added.
- When changing settings on the server side, all connected mbi clients are now informed (via server push message) - the change is then displayed there with a notification
- When using the PostgreSQL plugin, the driver version is now also displayed in the server information
- The underlying database layer has been revised for better access speed
- A file button for jumping to the directory has been added to "Files of a transaction"
- In addition to the detailed view of the files of a transaction, there is also a summary that contains only the most important files
- User-defined columns can now be customised per client
- The log filter in the transaction overview has been expanded to include the time of day
- The SKI extension can now be set for key generation in certificate management
- The client-server interface has been revised for better performance
- There is now a complete JSON integration in the EDI Converter
- Projects of type JSON can now also be set in the message identification
- For mail configurations (accounts/notification), the data of the underlying mail server (ports/security etc.) can now be found out after entering the mail address
- It is now possible to check the CRL (Certificate Revocation List) of certificates in the certificate manager
- There is a new renderer for all combo boxes that have to do with partners/messages
- The client-server interface has been revised for better performance
- The system load was not displayed correctly - now the inbound and outbound queue fill levels are also displayed correctly
- The task mbi_sendmail triggered a notification with a contained null pointer if no mail address was assigned to the recipient in the master data
- ANSI X.12 message identification: The time field in the GS segment is now 6 digits long - previously it was only 4 digits long.
- The REST API no longer worked if REST requests were received while the server was still running
- There was a memory leak in the security provider of the REST API
- Both REST API and web interface were running with unpooled database connections, which had a negative impact on performance
- Certificate manager: No CSR could be generated for EC key
- mbi_trfcsend terminated with a null pointer if the input data was not an IDOC
- mbi_trfcsend allowed to send empty files - but then the workflow was set to yellow and was not processed further
- mbi_trfc_send: A possible UTF 16 BOM is now removed during the file split of the IDocs
- There was a problem when exporting EC JKS keys to PKCS#12
- The priority of the message identifications (server settings-message identification) got mixed up when deleting entries from the list and adding new ones.
- (mbi 2022 Patch Level 1) The lines of the input adapters and the system tasks do not update correctly
- (mbi 2022 Patch Level 1) Input adapters, system tasks: There was a graphical problem that the log of executions was updated once per second - this prevented scrolling in the log of individual executions
- (mbi 2022 Patch Level 1) The EDIPad did not start correctly
- (mbi 2022 Patch Level 1) Input adapter: Newly added tasks cannot be executed immediately, the whole module had to be reloaded first
- (mbi 2022 Patch Level 1) x.400 did not fetch any data, but left all input data in the UAFINWIN/inbox directory - here the data had to be additionally fetched into the mbi via a poll
- (mbi 2022 Patch Level 1) x.400: The creation of a new account failed. However, there was no problem with existing accounts.
- (mbi 2022 Patch Level 1) The status of a transaction may not be set manually via external access before the message identification has been completed. However, this was possible.
- (mbi 2022 Patch Level 1) The UINotification has been revised
- (mbi 2022 Patch Level 2) The entries for the executable x.400 file in the server settings were extended by the current path. Since the defined x.400 path was then also added during execution, the x.400 executable ended up with an incorrect path
- (mbi 2022 Patch Level 2) When accessing a Linux mbi server from a Windows mbi client, the project explorer was not displayed in the resource overview of a transaction
- (mbi 2022 Patch Level 3) Splitted transactions become unreadable in the dark mode of the client
- (mbi 2022 Patch Level 3) HTTP keystore: You could not change an alias - you always had to delete the certificate and read it in again if you wanted to do so
- (mbi 2022 Patch Level 3) X.400 Send Pooled writes the data for collection to the wrong directory - a path separator was missing here
- (mbi 2022 Patch Level 3) PollX400: If a delivery was not successful, the "nondeliver" line is now always output in the log, for better error tracking
- (mbi 2022 Patch Level 4) In the workflow "collect_pooled_messages" the encoding could not be selected in the client
- (mbi 2022 Patch Level 4) Workflow parameters of type "List" could not be selected
- (mbi 2022 Patch Level 4) There was a synchronization problem in the message splitter, resulting in situations where multiple incoming messages overwrote their split results
- (mbi 2022 Patch Level 4) If multiple files were delivered via x.400 in one transaction and one of them failed, all involved transactions were set to failed
- (mbi 2022 Patch Level 4) The integrated JSON-XML converter had problems converting JSON data that was not available as a JSON object but as a JSON array