AC v3.7.1 release highlights

New features and improvements

  • Option to create a copy of an EDI Template/Transaction
    You can now create a copy of an existing EDI Template/Transaction and modify it as per your need. For more details, refer to this document.

  • Access to the transactions based on a project
    You can now access the transactions based on a project. To achieve this, you now have the following two capabilities in the product:

    • While creating a transaction, you now have the option to associate it with a project, resulting in the project-based access to the transaction. Earlier, the transactions were accessible based only on the Networks with which they were associated. 
    • To access the transactions based on a project, you need to have a Company Only type of role assigned to you. For more details, refer to this document.

  • Run Now option for an inactive Transaction
    You can now use the Run Now option to execute a Transaction manually even if the Template/Transaction is not in active state. For more details, refer to this document.

  • Support for OAuth in Microsoft Dynamics CRM connector
    You can now use OAuth as the authentication type in a Microsoft Dynamics CRM connector. For more details, refer to this document.

  • Support for Universal Connection Pool (UCP) in DB Info activity 
    You now have the option to select Universal Connection Pool (UCP) as the Connection Pool in a Database Info to help improve the execution time of the database activities. For more details, refer to this document.

  • Support for retaining the special characters in a JSON layout
    You now have the option to retain the special characters, for example, \n,\r, in a JSON data file by configuring the property abpm.connect.jsonschema.retainSpecialCharacters. For more details, refer to this document.

  • Upgraded Amazon Corretto JRE
    The bundled Amazon Corretto JRE has now been upgraded from v1.8.0_252 to v1.8.0_342 ensuring regular security updates.

  • Optimized AIMap performance
    To optimize the performance of AIMap, the low confidence suggestions in AIMap are now fetched in batches.

  • Support for custom Data Encoding
    You can now add and use a standard Data Encoding of your choice while creating a Template. For more details, refer to this document.

  • Access to Adeptia Connect License Server through proxy
    You can now connect to the Adeptia Connect License server for license verification even when you have installed Adeptia Connect server behind a proxy. For more details, refer to this document
    . 

Security enhancements

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

Bug fixes

The following bugs have been fixed with this release:

  • The value for Add On Configurations field in an FTP activity disappeared when the users opened it in edit mode.

  • Users were getting error while creating/updating a mapping using Developer Studio.

  • In the clustered environment, the execution of process flow was taking longer than expected when the Recoverable Process Flow option was enabled in it, and the shared path was Azure file share.
  • In a clustered environment, for some underlying causes, the AIMap was not able to start.

  • The application was not able to connect to the license server through proxy for license verification.

  • When XALAN Transformer type was used in the mapping, the mapping errors were not getting displayed in the Webmapper.
  • The value of the Password type of template/transaction parameter was visible in the View screen of the respective template/transaction.
  • The SEQUENCE function in  a mapping with was not working as expected when the mapping was executed in multiple Process Flows.
  • A user encountered a data truncation error while trying to edit and save an Excel Layout created by another Business User.
  • When the user uploaded a file in an existing Excel Layout -- created using a file -- and saved it, the Sheet Name value in the layout was shown in encrypted format in edit mode.
  • When GAC was enabled, the LDAP users were getting an unexpected error Unrecognized token 'Connect' while executing a Transaction. 
  • The application was getting sluggish due to the unrestricted growth in the size of the Catalina log file.
    • You can now set the property Dcatalina.log.file.size in the JVM parameters section of the launcher.properties file located at …<ConnectPortalInstallFolder>\ConnectPortal\conf to define the file size limit (in MB) beyond which the application creates a new instance of the file.
  • The Destination Routing String field in a SAP Client activity was mandatory and threw error when no value was provided in this field.
  • When a Business User created a copy of an existing Excel Layout created by an IT User, the Project of the copied layout got changed to Default.
  • The Connect Portal dashboard showed incorrect execution status of the Transactions/Process Flows.
  • When a user created an activity, for example, an Advance Database source as a non-admin user, and switched to an admin role, and then logged out, the activity either failed to execute or logged errors.
  • The database retained the jobs for the Transactions/Process Flows even when they were aborted due to system failure.

  • Certain DB activities were failing to execute.
  • Applying certain rules in the Mapping, for example, incomplete When condition caused the CPU usage to reach its limit and force the application to stop working.
  • It was taking longer than expected to trigger and execute a Transaction.
  • The Text Layout threw an error if the file being used to create the Layout had blank column headers and the Dynamic Header Support was enabled for the Layout.

  • While creating and executing a Text Layout, the headers were not being picked up from the Row Start Position set in the Advanced Properties.

  • Users were getting an error while creating an IDoc Layout of "Extension" type.
  • The mapping rules for a Data Mapping that had Namespace prefixes in the child element but not in the parent element got disappeared when the mapping was opened in edit mode.

  • The Mapping that had Namespace prefixes in the child element but not in the parent element was getting stuck at the time of loading.

  • Users were getting an error while executing an EDI outbound transaction with Content Based routing and having IDOC layout as the source.

  • When the same event was bound with multiple EDI Outbound Transactions having Content Based Routing, the dashboard displayed the execution details of only the Transaction wherein the Event was originally created.

  • The application was not able to connect to the license server through proxy for license verification.

  • Users were not able to select or create a REST Consumer with GET method while creating a Custom Template.

  • The execution of an EDI outbound relationship was failing as the Transaction Set Control number was going out in an incorrect format.
  • When \r\n was used in a JSON schema field as its value at the source, it caused a new line in the corresponding text Schema field at the target.

  • The users encountered errors related to:

    • Oracle SQL query

    • logininfo.txt file