AC v4.5.4 release highlights

New features and improvements 

• Added a new microservice,sapservice, for SAP integration
  You can now enable SAP service while deploying the application. For more details, refer to this page.  

Bug Fixes

• The application allowed an unauthenticated user (with external access to the web-application) to be able to access the Heapdump.hprof file.

  The application now secures the heap dump file using the secrets defined in the global values.yaml file under the webappGateway > environmentVariables section. You can define the secrets in the following two variables:

  Property	Description	Default value
  CUSTOMACTUATOR_SECURITY_USERS_0_USERNAME	The username required to authenticate access to heap dump.	"user"
  CUSTOMACTUATOR_SECURITY_USERS_0_PASSWORD	The password required to authenticate access to heap dump.	"adeptia123"

• The Process Flow using an Advanced Database Source (Oracle) took longer than expected to execute at runtime. 

• It took longer than expected to load or edit the Advanced Database and Database activities.

• The Data Mapper failed to load with the error "WebRunner is not reachable". 

• The application failed to consider the parameters specified in the Add On Configurations field of the FTP Account during the execution of a Transaction. 

• The response from the application's endpoints contained duplicate Vary headers indicating improper configuration. 

• When a Process Flow using Advanced Positional Layout at the Target failed due to invalid field length, no error description was recorded in the error logs. 

• The IDoc Extension field was empty when users edited an IDoc Layout, even though it was defined when the Layout was created. 

• Runtime microservice failed to start after the upgrade when the --add-opens parameter was included in the JAVA_OPTS variable under the deploymentmanager > runtimeImage section of the global values.yaml file. 

• ​The number of connection pools exceeded the maximum number of connections defined in the Database Info. 

• The application failed to process large files uploaded to the Azure Blob Storage Account using a Web Service Provider. 

• The Store Procedure that used existing DB Info failed to execute. 

• The distributed Child Process Flows sometimes did not work as expected because they used the outdated Parent Process Flow context stored in the Child context.
  This has been fixed by adding the variable initializeParentContextInChild for Call and Spawn Actions in Process Flow with its default value set to false. For more details, refer to this page. 

• The application failed to connect to the Kafka server intermittently. 

• Users were redirected to a Microsoft URL for authentication while creating an Azure Blob Account with Azure AD as the Access Type, despite providing the Client ID, Client Secret, and Tenant ID. 

  To ensure the fix works as expected, the app must be assigned Storage Blob Data Contributor role to access the Storage Account.

• The Context Info of the Process Flow was not visible on the Dashboard when a context variable, cookie, contained an array. 

• While creating a Transaction from a Template that contained a Checkbox type Transaction parameter with validation set for it, users were unable to select that parameter on the Parameter Values screen. 

• The Process Flow summary in the mail notification displayed the status as Running even after the Process Flow had been successfully executed. 

• When Optimized Processing was enabled in the Advanced Database Target and Filter Empty Elements option was selected in the Mapping, an error record was generated at the target if the fields containing values in a record differed from those in the first record.
  This issue has been resolved by introducing the Identical Columns Across Records checkbox in the Advanced Database Target, which is unchecked by default. 

  Enable this checkbox only if all records being saved to the database share the same set of fields containing values.

• The REST Provider in a Process Flow failed to execute on dedicated runtime deployment with the following error:
   "Unrecognized token 'PKIX': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 5]" 

• Mapping threw an error when there was a mismatch between the namespace prefix in the source XML and that defined in the splitter XPath.
  The following property has been added that you can set to true to resolve the issue. 

  Property	Description	Default value
  abpm.datamapper.data splitter.splitterxpaths.ignore NamespacePrefixMatch	Specifies whether to compare the XML input elements with the defined splitter XPath including the namespace prefix. Set this property to true to compare elements based only on their local names, ignoring the namespace prefix. Setting it to false includes the namespace prefix in the comparison. Navigate to Account > Settings > Microservice Settings > Runtime > Data Mapper section to configure this property.	false