A new minor release 4.5 is now available for download.
With the new OpenCelium Release 4.5, we are taking integration processes to a new level. This update is full of features that not only simplify operation, but also make your system landscapes more secure, transparent and powerful. Whether it’s intelligent conditional logic, improved debugging functions or enhanced data protection – version 4.5 gives you exactly the tools you need for smooth interface operation. Take a look at the most important new features and find out how OpenCelium can now make your integrations even smarter.
New feature in the connection editor: Support for AND/OR operators in conditions
With the current release of OpenCelium, we are expanding the options for defining conditions in the connection editor. From now on, complex logics can be mapped by using AND and OR operators within a condition.
In concrete terms, this means:
It is now possible to flexibly combine several conditions, e.g:
- Status = “open” AND priority = “high”
- Type = “Incident” OR Type = “Service Request”
What are the advantages of the new feature?
More flexibility:
Complex scenarios can now be mapped directly in the editor, without workarounds or additional logic on the system side.
Better data quality:
Only relevant data records are processed, which reduces the susceptibility to errors.
Extended application possibilities:
Ideal for interfaces where different criteria need to be fulfilled simultaneously or alternatively.
Clear processes:
Conditions can be traced directly in the interface – even with more complex sets of rules.
Time saving:
Less manual rework thanks to more precise filtering and control.
This extension makes OpenCelium even more powerful in the implementation of integration logic – without any programming.
New logging feature: Improved traceability and debugging of interfaces
Another highlight of this release is the revised logging concept for interface executions in OpenCelium. From now on, the logs are written to directories that contain the ID of the job. In addition, each individual execution of an interface is saved in separate files. The files are clearly named:
- Timestamp
- Connection-ID
- Execution-ID
Example:
2025-05-21_19-08_2_s_19.log
Configurable storage in the application.yml
In the configuration file application.yml, you can also define how many log files should be reserved for successful and failed executions – separated by status. This allows you to maintain an overview and at the same time control the memory requirements.
Logs directly in the UI – with search function
Another major advantage is that the latest success or error logs can be viewed directly in the OpenCelium interface. An integrated search function allows you to search for specific content or error messages – ideal for quick debugging without having to go through the file system.
What are the advantages of the new feature?
Better traceability:
Each interface execution is individually documented and traceable.
Fast troubleshooting:
Errors can be analyzed directly in the UI – even in a team.
Individual control:
The number of stored logs can be flexibly adjusted.
Efficient troubleshooting:
The new search function saves time when debugging complex integrations.
This new logging feature makes OpenCelium even more transparent and efficient in daily operation – especially in complex system landscapes with many interfaces.
New support feature: generation of support files for faster error analysis
To further improve support, OpenCelium now offers the option of generating a support file for each interface. This new feature facilitates error analysis and enables targeted support from internal or external support teams.
What does the support file contain?
The support file is a ZIP file containing the following components:
- The associated log files of the interface – optionally with customizable masking level to hide or completely remove sensitive data.
- The interface configuration itself to provide a complete technical context.
Data protection in focus
When creating the support file, the user can determine the extent to which sensitive content should be masked or removed. This ensures that data protection guidelines are adhered to – even when the files are passed on to third parties.
Central administration in the admin panel
The support files created can be conveniently viewed and downloaded in the admin panel under the new “Support files” tab. This enables quick access for administrators and support managers – without any additional manual steps.
What are the advantages of the new feature?
Quick problem analysis:
All relevant information bundled in one file.
Efficient support process:
Support teams receive full context without having to ask.
Data protection compliant:
Masking option protects sensitive data.
Central availability:
All support files available in one place in the admin panel.
This new feature increases transparency, improves communication with support teams and significantly reduces the effort required in the event of errors – a further step towards all-round professional interface operation with OpenCelium.
New security feature: protection of sensitive access data with master password
With the current release, OpenCelium introduces an important security function: Access data to third-party systems is now protected by a master password in the connector. This master password is stored centrally in the application.yml and prevents unauthorized access to sensitive information such as user names, passwords, API tokens or keys.
How it works
- The master password is defined once in the application.yml on the server.
- When this function is activated, the saved access data in the interface is masked and can only be viewed after entering the master password.
- Without the master password, access to this data remains blocked, even for logged-in users with extended rights.
What are the advantages of the new feature?
Increased data security:
Confidential access data is protected against unauthorized access.
Clearly separated roles:
Developers and integrators can maintain interfaces without having access to critical authentication data.
Simple configuration:
The master password is managed centrally and securely in the configuration file.
Protection at UI level:
Passwords and tokens remain hidden even in the user interface.
This feature is particularly aimed at organizations with high security requirements or multiple user roles and sustainably strengthens the protection of sensitive system connections in OpenCelium.
New feature: Field mapping now also available for request headers of an API operation
With the current release of OpenCelium, field mapping has been expanded to include another important use case: header fields of API requests can now also be mapped directly in the interface editor.
What’s new?
- In addition to the mapping of request body and URL parameters, it is now possible to fill individual header fields dynamically.
- The values for the header fields can be obtained as usual from previous steps of the interface or defined statically.
- Mapping is carried out directly in the familiar editor and is fully integrated into the configuration process.
Application scenarios
- Authentication: Automatic setting of tokens such as authorization, X-API key or bearer headers.
- Custom header logic: Transfer of dynamic values such as session IDs, user information or system identifiers.
- Header-based control: Support for APIs that use filters or routing mechanisms based on header fields.
What are the advantages of the new feature?
Even more flexible interface design:
More control over the entire API call – even in the header.
Reduced manual effort:
No more manual adjustments to the header outside the editor.
Better support for modern APIs:
Compatibility with systems that require header-based security or configuration.
Centralized maintainability:
All mappings – body, URL and header – can now be configured in one place.
This feature makes OpenCelium even more powerful – and now offers even more options for the seamless integration of modern APIs.
Here is the detailed changelog
OpenCelium 4.5 (deutsch)
[Neue Funktion]
Support File Generierung
[Neue Funktion]
Feldmapping im Request-Header
[Neue Funktion]
Operatoren mit AND und OR support
[Neue Funktion]
Konnektor-Einstellung durch Master-Password geschützt
[Bug][OC-999]
AllowList funktioniert nicht mit ganzen Zahlen
[Bug][OC-992]
Zähler für die Anzahl der ausgeführten API-Operation prüfen
[Bug][OC-1119]
Das Speichern eines Aggregators fügt doppelte Kommentare hinzu
[Bug][OC-978]
API-Request-Body unterstützt den ARRAY-Typ nicht
[Bug][OC-998]
Fehler: “Enhancement Not Found”
OpenCelium 4.5 (english)
[New feature]
Support file generation
[New feature]
Field mapping in the request header
[New feature]
Operators with AND and OR support
[New feature]
Connector setting protected by master password
[Bug][OC-999]
AllowList is not working with integers
[Bug][OC-992]
Check counter of the operation usage
[Bug][OC-1119]
Saving an aggregator adds duplicate comments
[Bug][OC-978]
API-Request body doesn’t support ARRAY type
[Bug][OC-998]
Error: “Enhancement Not Found”
becon blog
CONTACT
Get in touch with us!
Do you have any questions, suggestions, requests or are you facing a particular challenge? We look forward to hearing from you!