Release Build: 10.06.2026
Deploy Date: 10.06.2026
Fix version: ONE_RE_6_6_15
Release description:
With version 6.6.15 the focus is on the handling of failed digital payments, the further optimization of IAM data management and the technical modernization of reporting. The release includes 10 functional enhancements.
Three highlights stand out in particular:
Failed Digital payments via Wallee are newly recognized and actively communicated: Previously, a FAILED_PAYMENT status remained stored in the database without the system reacting - errors only became known through customer messages or triggered dunning cycles. The support team is now notified by email when a payment fails. In addition, failed payments are visible in the Open Items Statistics so that affected invoices can be specifically identified and processed manually. In the event of an error, workflow processing now correctly redirects to the error case instead of continuing silently.
The Collection lists Reports are being migrated from the resource-intensive Crystal Reports framework to the new json2pdf solution as the first wave of migration (~5 reports). Crystal Reports require a proprietary runtime environment and are the main reason for the oversized heap memory of the reporting service (Xmx 27 GB). With json2pdf, the same tabular reports are generated in a much more resource-efficient way. The migration creates the basis for the gradual replacement of other Crystal Reports reports in future releases.
The IAM Login Data Import Performance will be further improved: Based on the database indices from version 6.6.14, the import logic itself will be fundamentally revised with batch inserts, updates and optimized SQL statements. At the same time, the customer service view has been given a manual refresh button for immediate synchronization with the IAM system - without having to wait for the next automatic import cycle.
⚙️ Changes & extensions
IAM & user management
-
ONE-7499 - The IAM Login Data Import logic has been fundamentally revised with batch inserts, batch updates and optimized SQL statements. The database load is significantly reduced, especially for large amounts of session and event data. The import runs reliably within the configured batch job interval.
-
ONE-7492 - A manual refresh button is now available in the customer data area (IAM login data), which triggers an immediate synchronization of the Keycloak data for the open account - without reloading the page and without having to wait for the next automatic import cycle. The batch job interval is extended from 15 minutes to 1 hour. A status column is now displayed in the session overview: active sessions are marked in green, inactive sessions in red. The event list is now sorted in descending order by timestamp.
-
ONE-7439 - All system users now use Keycloak Client Credentials (Client Secret) instead of Basic Auth. This means that sessions are no longer created and orphaned sessions, which previously used resources unnecessarily, will be prevented in future.
Finance & Accounting
-
ONE-7567 - Failed digital payments (Wallee status FAILED_PAYMENT) are newly recognized and actively handled: The support team receives an immediate email notification. Failed payments are now visible in the Open Items Statistics (for companies with New Finance). The workflow now correctly redirects to the error path in the event of payment errors instead of silently closing the process as successful.
-
ONE-7505 - For companies with an active New Finance system, follow-up invoices now correctly adopt the payment method of the original webshop order. Previously, follow-up invoices were always created with the INVOICE payment method, regardless of whether the initial order was placed by credit card or another payment method.
Reports & Reporting
-
ONE-7514 - The collection list reports (~5 reports) will be migrated from Crystal Reports to the new json2pdf framework. The reports affected include the billing journal, petty invoices, invoice journal and tenant-specific variants. The previous .rpt files will be retained as a fallback. Tenant-specific .rpt files that are no longer required will be removed on vasmiq007 and vasmiq011. The new ASMIQ.ONE templates module provides the JSON configuration files.
Deliveries
-
ONE-7526 - When starting a new delivery registration, the system checks whether registrations already exist for the selected delivery date. If yes, a warning dialog appears with two options: "Replace existing registration" (default) or "Add new entries (replace duplicates)". The user decision is logged. Without existing entries, the registration runs as before without a dialog.
Master data & CRM
-
ONE-7523 - The address history now shows two additional columns: "Address valid from" and "Address valid to". These show the actual validity period of an address entry - similar to the existing display in the subscription history. The previous columns "Changed on" and "Changed by" remain unchanged.
Technical improvements
-
ONE-7424 - A new API log is available for all services. API calls can be logged, traced and restored in the event of an error. Access is via JPA/Hibernate or an internal API endpoint.
-
ONE-7417 - The Liquibase changelog files now use an XML schema file stored locally in the project instead of the online download from liquibase.org. This prevents HTTP 429 errors (too many requests) during parallel database updates, reduces network traffic and increases deployment stability.
|
Issue Type |
Priority |
Key |
Summary |
|
|---|---|---|---|---|
| 1 |
Change |
Prio 1 - Major |
Optimize performance for IAM login data import |
|
| 2 |
Change |
Prio 2 - High |
Implement Collection Listen Reports with json2pdf |
|
| 3 |
Change |
Prio 3 - Medium |
Handle Failed Digital Payments |
|
| 4 |
Change |
Prio 3 - Medium |
Warning for Duplicate Expedition Registration on the Same Delivery Date |
|
| 5 |
Change |
Prio 3 - Medium |
Address History: Add "Address valid from" and "Address valid to" columns |
|
| 6 |
Change |
Prio 3 - Medium |
Follow-up Invoices ignore Original Payment Type for Companies using new Finance Module |
|
| 7 |
Change |
Prio 3 - Medium |
Add Manual "Refresh" Button for IAM Events in ASMIQ.one |
|
| 8 |
Change |
Prio 3 - Medium |
Handle sessions opened by legacy.service.user |
|
| 9 |
Change |
Prio 3 - Medium |
Introduce a log possibility to better track, monitor & help recover API calls |
|
| 10 |
Change |
Prio 3 - Medium |
Change liquibase changelog files to use local dbchangelog.xsd file instead of online |