Skip to main content

Hotfix - Incorrect Binary Encoding in REST Requests

· One min read
Robert Loipfinger
Cirlce Lead Platform @ ADITO

Hotfix versions 2024.2.5.3, 2025.0.4.1 and 2025.1.0.1 of the ADITO Platform have been released.

What changed

A bug in the handling of outgoing REST web service requests using the DATA_BINARY entity type not using multipart has been fixed. Since platform version 2024.2.0, the request body was erroneously Base64-encoded, even though the payload is expected to be in binary form. This additional encoding occurred regardless of the intended transmission format.

Why it matters

External systems receiving such requests expected raw binary data (e.g., for application/pdf, application/octet-stream). The unintended Base64 encoding altered the content and led to processing errors or integration failures.

If you use DATA_BINARY in REST service calls without multipart encoding, and the receiving system expects raw binary payloads, you should apply this hotfix to ensure correct transmission behavior.

2025.1.0 released

· 2 min read
Robert Loipfinger
Cirlce Lead Platform @ ADITO

With version 2025.1.0, the ADITO platform delivers a range of technical improvements that directly benefit development, administration, and integration processes.

Below is a brief overview of selected changes:
View the full release notes

CKEditor: First step toward AI-assisted content creation

An AI assistant is now integrated directly into the editor. It is connected to ADITO’s own infrastructure, fully hosted in Germany and compliant with all GDPR requirements.

Microsoft Graph: New Exchange calendar integration

For the first time, the platform can access calendar data via Microsoft Graph. This lays the foundation for broader Microsoft 365 integration.

JDito: Modern scripting with extended language support

The embedded JavaScript engine (Rhino 1.8.0) has been updated, enabling the use of modern language features such as advanced control structures and functions.

REST web services: More robust, efficient, and predictable

REST interfaces can now be configured more precisely and integrated more reliably with third-party systems. Several technical improvements enhance behavior under load and reduce unnecessary resource consumption. This simplifies external API integration and improves overall system stability.

Designer: Improvements for module development

The Designer includes multiple enhancements that improve traceability and reduce maintenance effort. These changes support more reliable configuration, particularly in complex data models and rule-based logic.

Lookup, TreeTable, validation: Fewer inconsistencies, better defaults

Various fixes improve the behavior of lookup fields, tree components, and validation logic. In particular, multi-value inputs now behave more consistently, with better handling of empty values and increased reliability in custom forms.

Infrastructure: Up to date and cleaned up

Numerous technical dependencies have been updated in the background, including PostgreSQL, Ignite, Quartz, and all JDBC drivers. These updates reduce technical debt, improve long-term maintainability, and minimize the need for manual error handling at runtime.

Feedback appreciated

· One min read
Robert Loipfinger
Cirlce Lead Platform @ ADITO

We’ve added a feedback button to this site. You’ll find it on every page at the bottom right.

See something that’s missing, confusing, or just not good enough? Let us know.

Feedback is quick, anonymous if you want, and always welcome. Want to hear back from us? Just leave your name or email: we’re happy to get in touch.

This documentation is built for you and it gets better with every bit of feedback.

Thanks for helping us improve.

./Robert

Welcome

· One min read
Robert Loipfinger
Cirlce Lead Platform @ ADITO

Nice to have you here. This site is for everyone working with our platform – whether in development or operations.

We build software that does more than the usual. To keep it that way, our documentation also has to do more than just explain features. It should provide clarity, guidance, and support decision-making. In short: it’s part of the product.

That’s why we’re rethinking how we do documentation.