AC v3.7 release highlights

Owned by Ashhad Alam
Last updated: Apr 27, 2023 by Shruti Pasayat
5 min read

New features and improvements

  • Support for Context Variable based routing 
    You can now execute a Transaction with REST or SOAP Webhook at Source, based on Query and Header parameters defined in the corresponding Template with Context Variable Based Routing.

  • OAS 3.0 standards API documentation for REST Webhook Transactions 
    Adeptia Connect now creates the OAS 3.0 standards API documentation for a REST Webhook Transaction. You can also edit the API documentation as when required. Using this API documentation, you can also execute a REST Webhook Transaction.  For more details, refer to the pages Adding API documentation, Using API Documentation for REST Webhook Transaction, Defining a Convert Inbound Source Application.

  • Addition of GET and DELETE methods for Advanced REST Webhook 
    Adeptia Connect now also supports GET and DELETE methods for an Advanced REST Webhook that you may want to use as a Source in a Template.

  • Deletion of saved REST Webhook attachments
    You can now configure a Template (with REST Webhook as a Source) to delete the attachments that are saved after the successful execution of a Transaction based on that Template. You can also configure a REST Provider – published as a Process Flow, having either PUT or POST method – to delete the attachments saved after its successful execution. For more details, refer to the pages Defining convert inbound source, and creating rest provider.

  • Support for custom email headers 
    You can now add custom email headers that you may want to include while you’re at Define Target Location step in a Template, creating a Mail Notification, or creating a Mail Target activity. 

  • Enhancements in Advanced Text Layout
    >> You can now specify a field that you want to use as the record identifier in an Advanced Text Layout. For more details, click here.
    >> You now have the option to ignore a record that does not hold any value in any of its fields, including the record identifier. 
    >> The Min Size and Max Size fields in the Advanced Text Layout now have predefined/default values of the character count. You can change these default values based on your requirement.

  • Option to allow more fields with Dynamic Header Support enabled in the Text Layout 
    When you enable Dynamic Header Support option in the Text Layout (created using Default option or Layout Builder), the Text Layout can now be executed successfully even if there are more headers than defined in the layout. 

  • Support for selecting a Post Process Type (Transaction or Process Flow) by a Partner
    While creating a Template, you can now allow partners to select the Post Process Type (Transaction or Process Flow) at the Choose Process step at the destination having Post Process as the Target. 

  • Login restricted for users with no LDAP role mapping
    You can now restrict the users to log in to Adeptia Connect if their LDAP group is not mapped to a Role.

  • Layout Builder for creating Advanced Database Layout 
    >> You can now create an Advanced Database Layout using the Layout Builder.
    >> A query editor has been introduced to retain and render a well-formatted structure to the query written therein.
    >> You can now use the placeholder to provide a value for a parameter in the dynamic where clause in the query editor to create the Advanced Database Layout.

  • Email Notification on Kafka Listener failure
    You can now provide the email id(s) separated by commas to receive notifications in case of Kafka Listener failure. For more details, click here.

  • Restriction on saving a mapping when external validation fails
    You can now choose to restrict saving the mapping until the external mapping validation succeeds. For more details, click here.

  • Cross-field validation on transaction parameters
    You can add validation to a transaction parameter (field) to define a rule for dynamically performing a resultant action on another field (target field). For more details, click here.

  • Enhancement in Connect Portal installation
    The system now enables you to proceed to the next steps of Connect Portal installation even if connection to the Connect Server fails. For more details, click here.

  • Support for third party tools to capture migration logs
    You can now capture the migration logs using a third party tool.

  • Option for the Partner to define the Database Source and Event individually in a Template
    While creating a Template, you can now allow a partner to define the Database Source or Database Event or both, as there are now two distinct pages (with "Partner will define this step" option) for defining them.

  • Landing to a desired page in case of multiple IdPs 
    The users can now land on to the desired page in Adeptia Connect even when you are using multiple IdPs for SSO. For more details, click here.

  • Support for Email app at Destination in EDI Inbound/Outbound Transaction
    You can now also use Email as the destination app in an EDI Inbound/Outbound Transaction.

Security enhancements

  • Vulnerable third-party jars have been upgraded to remove critical and high vulnerabilities in those jars. 
  • The encryption key is now saved in encrypted format instead of plain text for enhanced security.

Bug fixes

The following bugs have been fixed with this release:

  • While creating or updating a Database Info, the test for database connection failed with an error when they used a password containing any of the special characters (?,#,{,},[,],") in the Password and Confirm Password fields.

  • After upgrading to AC v3.5, while viewing or editing an existing Transaction, the users were not able to view the Transaction parameters though they had been defined at the Template level.

  • It was taking longer than expected to open a transaction in edit mode.
  • Users were not able to set the size limit for the file to be uploaded in the Data Mapper.
  • The FTP Event was not able to fetch the hidden files from the FTP server. 
  • The maximum length for a Network parameter of Combo type was restricted to be only 48 characters long.
  • Users were getting error while running the checklist utility and hence could not perform AIS to AC migration.
  • Users were not able to download files from the specified folders in the Azure Blob container.
  • Users were not able to edit the FTP Target associated with an EDI Transaction migrated from AIS to AC.
  • The special characters in the name of a file when read from Amazon S3 bucket were replaced by percentage (%).
  • When the users tried to execute a Transaction using BambooHr at Source, the Transaction failed to run.
  • The application threw an incorrect error message while testing an Excel Layout with a file having an empty header row.
  • The Excel Layout was not throwing an appropriate error message on its testing or execution when it used an xls file that contained an empty row above the header row.
  • The Excel Layout was not able to process a password protected xls file.
  • The users were not able to activate a Transaction when they used SFTP as a Source/Target in the respective Template/Transaction.
  • After applying the patch Release_6_9_1_18_30Dec_2021, users were not able to view and select the LAN Target variable names in Put-Context-Var action in a Process Flow.
  • The execution of a Process Flow/Transaction failed when the users used UTF-16 character set encoding in the source XML layout.
  • The View option of a Template/Transaction displayed incorrect polling frequency for the source activity.
  • System threw an error when the user tried to open the Diagnostics page in Adeptia Connect.
  • The response to the API for copying a Layout or Mapping had formatting issues – users were not able to create JSON Layout based on the response.
  • The system displayed incorrect RAM usage for Connect Portal in the System Console.
  • The execution time of Database Source activity in a Process Flow has been improved by adding the property abpm.databaseinfo.connectionpool and setting its value as hikari under the category Adeptia Connect in the server-configure.properties file.
  • In case of an EDI transaction having multiple translations, the acknowledgement generated out of its execution contained duplicate entries of the segment when the source file had some errors in that segment.
  • The system threw an error while creating a JSON layout when any of the keys in the JSON file was a negative number.

  • Users were not able to view complete information of a Mapping on the mapping PDF.

  • The Azure Blob Event picked up all the files even when its Trigger Type was set to "new and updated files".
  • Users were not able to use BigCommerce as a source or target in a template.