AC v3.7.2 release highlights

New features and improvements

• Upgraded Amazon Corretto JRE to version 17
  The bundled Amazon Corretto JRE has now been upgraded from Java version 8 to version 17 ensuring regular security updates.
  

• Token-based authentication for NetSuite
  You now need to use token-based authentication to connect to a NetSuite account. Click here for more information.

• Support for exporting objects without repository folder in offline migration.
  While performing offline migration, you can now export objects without creating the Process flow repository files. For more details, refer to the documents on Export and Backup using Windows and Linux.

• Support to send complete error details via Email notification in case of EDI transaction failure.
  The translation error details will now be sent as an attachment with the email notification in case of a failed EDI Inbound/Outbound transaction ( for X12, EDIFACT and HIPAA EDI standards).

• Support to activate/deactivate multiple activities.
  You can now choose to turn ON/OFF multiple Transactions, Events and Templates from the list displayed on the current page for each of these activities.  For more details, refer to the documents

• Support for NTLM authentication in Mail activities.
  You can now use NTLM authentication type while creating any of the following activities:

  1. Mail Source

  2. Mail Target

  3. Mail Event

  4. Mail Notification

• Support to use context variable in the archive folder path in EDI template/transaction
  Now, you can also enter a context variable to define the name for the archive folder in case of EDI Transaction/Template.

• Enhancement to define firing schedule for Events, Transactions, and Templates using two cron expressions
  You can now make use of a second Cron Expression to define the firing schedule for a separate condition or address a condition supplementary to the first. The list of supported Events and Applications for a Transaction/Template are as follows:

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:

• A transaction with Azure Blob application as the source, failed to pick specific file mentioned in the Specify the file name & type that is to be processed field (on Select File Location screen) and instead processed all files present in the folder.

• Some segments in the EDI Acknowledgement File were not getting generated as per EDI Standards. This has been fixed by adding the property abpm.edi.removeSegmentSuffixAndLoopPrefix. You can set the value for this property to yes to remove the suffix from a segment's name and the prefix from a loop's name to be recorded in IK3 segment in 999 or 997 acknowledgement file. Follow the steps given below to configure this property:
  
  1. Click Account > Settings.
  2. Expand the Server Nodes Settings in the left panel.
  3. Select the server node.
  4. Click Edit.
  5. Go to Solution Properties > EDI Solution Parameters.
  6. Set the abpm.edi.removeSegmentSuffixAndLoopPrefix to yes.
  7. Click Save.
  8. Click Reload to bring the changes into effect. A confirmation message is displayed confirming that the configuration has been reloaded.
  9. Restart the Connect Server.

• The users were not able to expand some sub loops when they loaded the EDI Layout on Source and Target mapping.

• After applying the patch AdeptiaConnect_3_7_01_04_22Feb2023 the Migration Utility stopped working.

• After AIS to AC migration, users were getting an error and not able to proceed to the next step while trying to update the FTP Target in an existing transaction.

• After setting a value for the Mode Type field (on the File Generation Policy screen) in an EDI Transaction and moving to the next step, the application was resetting the field's value to Create when the users visited the Choose App screen (under Set Destination category) again without saving the Transaction.

• Users were able to access some of the REST APIs even when they did not use any authorization in the request.

• Users encountered an error while trying to update the Routing Type for an existing EDI Outbound transaction having Content Based routing.

• The PDF generated in the EDI interchange logs pages for an EDI Transaction was not in correct format when Advanced Positional Layout was used at the Target.

• After the execution of an EDI Inbound transaction, the EDI X12 Interchange log for the transaction on the Dashboard did not show the link to the output file in the FILE > OUT column.

• In case of multiple EDI Inbound transactions using the same template, even when no transaction had the trading partner id same as that in the Source, the system showed logs for the first transaction.

• When the users hit a specific REST API, they were able to see sensitive data even when they were not logged in to Adeptia Connect application.

• The users were getting an error message on the Web Process Designer when the stream generated from an activity was not being consumed.

• On changing the alias name of a CALL action in a Process Flow, the associated variables were not displayed in the Variable Name field of the variable's Activity Properties screen.

• The users were not able to change the property values for an existing Record Queue Producer migrated from AIS to AC.

• After migrating from AIS to AC, the users were not able to make and save any changes to an existing Process Flow's activity that had spaces in its alias name.

• While creating a Transaction, it was taking longer than expected to load the Partners on "Choose partner" screen.

• The users were getting the error "You have not given Related Key" when they clicked OK on the Select Schema screen while creating an Advanced Database Layout.

• Users were not able to save changes to the records while creating or editing a Positional Data Dictionary.

• While creating an Advanced Positional Layout, when the users used Data Dictionary, they were not able to make and save changes to the records.

• AIMAP service failed to start on Linux-based systems.

• Some UI elements were not working properly after the recent browser updates.

• Users were not able to open the applets because of the expired certificate.

• The users were not able to move to the next screen when they selected an EDI specification and clicked OK on the Select EDI Specification screen while creating an EDI Layout.

• In a Template/Transaction, when the users used Amazon S3 with its Bucket in the US East zone, the application threw an error while browsing the file on Select File Location step.