Skip to main content
Version: 4

AC v4.7.1 release highlights

New features and improvements ​

  • Support for validating Required fields mapping 
    You now have the option to validate whether all Required fields in the target layout are mapped before saving a mapping. This validation is enabled by default. To configure this behavior, go to Account > Settings > Microservice Settings > WebRunner > WebMapper and set the property abpm.services.webmapper.validateRequiredFieldsMapping to true or false, as required.

  • Support for multiple JVM parameters
    You can now specify multiple JVM parameters for the runtime microservice in the global values.yaml at:
    global > deploymentmanager > runtimeImage > JAVA_OPTS

  • **Expanded JVM parameters limit
    **The JVM parameters field has been expanded to allow up to 4,000 characters, enabling more advanced and flexible runtime configuration in dedicated deployments.

Bug Fixes​

  • While deploying the application on Amazon Red Hat OpenShift (ARO), if the SecurityContext variables were left blank, the RabbitMQ operator would automatically set their value to 999. 
  • Process Flows that used JTA-Begin, JTA-End, or JTA-Rollback actions sometimes failed to execute.
  • The upgrade failed when immutability was enabled for the migration-chart-emb and runtime-chart-emb config maps, and configuration changes were attempted on them.
  • Runtime Helm read the node selector and tolerations from its local values.yaml instead of the global one; it now reads them from the global file.
  • The microservices were reading containerPort values from their local values.yaml instead of the global values.yaml.
  • Users encountered an error in AC v4.x when opening a Mapping that was migrated from AIS. The issue occurred when the Disable Output Escaping property was enabled for a destination field.
  • While creating an export package with Individual Activities as the export criteria, when the user selects all activities and then deselects them, the package is still generated.