Version 5.4

<< Click to Display Table of Contents >>

Navigation:  Appendix > Version history >

Version 5.4

The following is a list of new features and significant changes in !MC5 version 5.4.x with references to corresponding manual entries where available. The complete list of changes in all versions can be found in !MC5 via the menu item Help / Check for Updates.

 

Version 5.4.30

 

EP Scripting timer scripts can now also be executed daily at a fixed time. The timer control settings have been revised and now show in which time periods or at which time a script is executed in each case. The overview also shows when the next execution is scheduled and when the script was last executed (See Reference / Settings / EP Scripting / Scripts).

Furthermore, timer scripts can now be executed directly from the !MC5 interface for testing. In contrast to the timed execution, where the console window is not displayed and closed directly after execution, the console window is displayed when testing from the interface and remains open after execution.

A new global timeout for EPS scripts prevents scripts from "hanging" and preventing the execution of further scripts. This can happen, for example, by unexpectedly waiting for user input in the script, which is not possible during timed execution. If the execution of a script is not completed after the time set for the global timeout has elapsed, the script execution is automatically terminated.

 

Version 5.4.25

 

In the partner settings of OFTP/OFTP2 partners a new placeholder for inserting a timestamp can be used in the Template (receive) (see Reference / Partner Management / OFTP/OFTP2 / File Settings).

 

Version 5.4.23

 

The grouping of OFTP/OFTP2 partners has been revised in this version (see File transfer / OFTP / Partner groups / Adding partners to a new group). Groups are now created/edited directly in the partner management instead of simply specifying a group name in the partner settings. Furthermore, incoming connections from partners in a group are displayed in the status under the group name, not under the name of one of the partners from the group as before.

 

Version 5.4.19

 

UserLookup tables can now be edited directly in the EDI-Convert Manager.

For analysing problems with the certificate validation a detailed log of the validation can be displayed in the certificate preview.

If the connection parameters are specified correctly in the SFTP client settings, directories on the server can be selected via dialog (see File transfer / SFTP / SFTP partner setup / SFTP Client). For this purpose, a direct connection to the server is established. This is helpful if the directories specified by the partner for upload and/or download do not correspond to the required, complete paths on the server.

 

Version 5.4.17

 

It is now possible to give files a different name during upload via SFTP client. After a successful upload the file will be renamed back to the original name on the server (see File transfer / SFTP / SFTP partner setup / SFTP Client).

 

Version 5.4.16

 

The module SFTP Server is available from this version (see File transfer / SFTP). This module allows partners to connect to your !MC5 via SFTP and to download and upload files. The focus of the SFTP server of !MC5 is especially designed for the transfer of EDI data as well as security and ease of use: A partner connecting to !MC5 with any SFTP client will only not see any directory structure, so he does not have to use a special server path and cannot create any directories or change to other directories. Only the files provided to the partner are displayed and when they have been successfully downloaded, they are automatically no longer visible to the partner and are internally marked as "sent". The SFTP server of !MC5 also does not allow any shell access, only the SFTP subsystem is supported.

 

Version 5.4.11

 

Under Automation all rules for the automation of !MC5 are now summarized in one overview, which were previously distributed among the items Autoversand (send files directly to a partner), EDI Rules (import EDI messages to be sent and export received EDI messages via the module EDI) as well as Automatic File Import (import externally received EDI messages). The central administration of the automation rules makes it easier to keep track of the processes in !MC5, from where files are captured and to where files are written. For better clarity the automation rules can be grouped and sorted by different criteria.

 

Version 5.4.10

 

Details from the certificate preview can be copied to the Windows clipboard via the context menu.

If the certificate contains information about callback lists, the corresponding URLs can be opened via the context menu in the certificate preview in the standard browser of the system.

 

Version 5.4.0

 

The SFTP Client module is available as of this version (see File transfer / SFTP ). With the SFTP Client module, data can be uploaded to and downloaded from an SFTP server. Until now, transfer methods other than OFTP could only be realized in !MC5 by controlling external programs using the add-on EP Scripting, which is still possible. For SFTP connections, however, this is no longer necessary.

TLS 1.3 is supported for all encrypted connections starting with this version. This also includes OFTP2 connections. TLS 1.3 is not yet part of the OFTP2 guidelines, but with the support of the latest TLS version you are already future-proof with !MC5 and can use encrypted connections with increased security, if the other side also supports TLS 1.3.

The OFTP2 certificate management has been further improved. Up to now, newly imported certificates (own as well as partner certificates) were always used from the time they were valid. Starting from this version of !MC5 you can set for each certificate the time from which it should be used. If your partner sends you a new certificate, you can now import it directly and set it to be used automatically from the time specified by the partner.

If you have activated encrypted connections via HTTPS for the HTTP client, you can now choose which TLS versions the HTTP client server should offer, including TLS 1.3 (see Reference / Settings / !MC5 / HTTP Client).