Skip to main content
Version: 4

AC v4.7 release highlights

New features and improvements ​

  • Expanded deployment options 
    In addition to Azure AKS, the application now supports deployment on Red Hat OpenShift ARO and Amazon EKS, giving you greater flexibility and choice for your cloud infrastructure.

  • Migrated to Red Hat UBI-based Docker images
    We have migrated from Alpine-based Docker images to Red Hat UBI (Universal Base Image) for enterprise compliance and security hardening.

  • Improved usage report 

    You can now monitor the monthly usage by viewing the usage report. The usage report now also includes the following usage information:

    • Total number of Transactions or Process Flows executed. It counts both parent and child Process Flows.

    • Total volume of data received by all the sources, including the Web Service Consumers.

    • Total number of activities and actions executed in all the Process Flows and Transactions.

  • Show only required destination fields in Mapping 
    You now have the option to display only the destination fields marked as required in Mapping.

  • Enhancements in Helm chart
    The Helm chart now includes improvements for more secure and efficient secret management.

  • **Perl package no longer bundled
    **Removes the Perl package from Docker images, reducing image size and mitigating potential security vulnerabilities. Equivalent functionality can be achieved using awk.

Security enhancements 

  •  Vulnerable third-party jars have been upgraded to remove critical and high vulnerabilities.

Bug Fixes

  • When the abpm.solution.edi.controlNumberGenStrategy property was set to sequence, the application sometimes allowed multiple Runtime Pods to concurrently read the same sequence number, leading to duplicate control numbers being assigned to outbound files for the same partner. 

  • Users were unable to create an Advanced Database Layout using the Layout Builder when the database table used to create the Layout contained column names with spaces.

  • When a Process Flow using an Advanced Database Source (with Optimize Algorithm enabled) was executed, columns with spaces in their names were not generated in the repository XML.

  • In the View Transaction screen, the EDI ROUTING RULE section (under Destination) incorrectly displayed EDI Configuration details instead of the corresponding EDI Routing Rule details.

  • When users edited a Transaction/Template created with Azure Blob as the source, the Send mail notification for no data on trigger and Send mail notification for error on trigger options were unchecked, even though they had been enabled while creating the activity.

  • When an Excel Layout configured with multiple sheets and the Process All Sheets option enabled was executed in a Process Flow using an input file whose sheet names differed in letter case from those in the file used to create the layout, the file processing failed.

  • When users edited an Azure Service Bus or Azure Blob account, the Use Config option was unchecked even when it was enabled while creating the activity.

  • When a user edited a Transaction/Template with Azure Blob as the source, the Trigger in Sequence option was disabled even when it was enabled while creating the activity. 

  • When the users enabled Filter Unmapped Elements in Data Mapper, the output of the mapping incorrectly included those unmapped elements with which comments were associated.

  • The Import Users button was not visible on the Users page when multi-mode (SAML and LDAP) authentication was enabled and the user logged in via SAML.

  • A Process Flow failed to execute when handling a large Excel file.
    A new property, abpm.schema.excel.poi.maxByteArray.size, has been added to configure the maximum number of bytes that can be processed from the Excel file at a time.

  • It took longer than expected to generate output in the Data Viewer.

  • When large number of Transactions were created using a Template with Context Based routing, their execution took longer than expected.

  • The Process Flow execution was slower than expected when a large number of Transactions were created from the same template and one of them was called in the Process Flow.

  • Navigating through the wizard steps while editing an existing Transaction took longer than expected.

Known issue: JTA actions causing Process Flow failure

Process Flows that use JTA-Begin, JTA-End, or JTA-Rollback actions may fail to execute. A fix is planned for the upcoming release (v4.7.1), scheduled for December 2025.