.png)
There are several innovations for interfaces and data exports in this release, which mainly ease operation and error analysis. Incoming API calls can now be logged, monitored, and re-executed as needed, in a configurable way. Importing interfaces can use their own error interface, exporting interfaces a preview function before the actual export. In addition, interfaces can now be duplicated with one click.
Previously, when there were problems with incoming API calls, it was often difficult to trace when which request arrived with which result. The new logging function provides relief here: via two new interfaces, incoming calls can be filtered by status, request and response data, duration, IP address, and user, and re-executed if needed. There is also progress on error handling: importing interfaces can now automatically trigger a dedicated error interface as soon as a rollback occurs, and the original faulty request is saved for further analysis. For exporting interfaces, it was previously a blind flight whether the exported data really matched expectations; the new preview function shows the result of a configured query directly in the export interface before the actual export is triggered. This reduces faulty exports and builds trust for critical data deliveries to customers or partner systems. And anyone who frequently creates similar interfaces for different partners or formats saves a lot of time with the new duplicate function compared to previously rebuilding manually from scratch.
You activate logging of incoming API calls via the new configuration interface "APILogConfig"; all logged calls can then be viewed, filtered, and re-executed as needed in the "APILog" interface. You store the error interface directly on the respective importing interface; the token for the error message is available to you for both importing and exporting interfaces. You activate the preview function by storing your own query of type "query for preview function" on the exporting interface. You trigger duplication of an interface via the new button directly in the interface overview; all settings are carried over in the process. For interfaces used in production, it is recommended to first activate logging with a short retention period and observe the data volume before defining a permanent configuration.
