Skip to main content
Version: 4

AC v4.3.04 release highlights

New features and improvements ​

  • **Support for migrating objects using APIs
    **You can now migrate objects from one Adeptia Connect environment to another using APIs provided by Adeptia. To learn more, refer to this page. 

  • APIs to deploy JAR and WAR files
    You can now deploy JAR and WAR files using APIs provided by Adeptia. To learn more, refer to this page. 

  • APIs to upload JAR and Class files 
    You can now upload a JAR or Class file to the the customClasses folder using the APIs provided by Adeptia. To learn more, refer to this page. 

  • Support for APIs based migration using Jenkins
    Adpetia now provides export, import, and rollback pipeline files that use migration APIs to perform automated migration through Jenkins. Click here for more information. 

  • New set of OAS 3.0 document based app connectors
    Adeptia Connect now integrates the following app connectors that use a document (OAS 3.0) based framework.

  • Support for creating CDATA custom connector
    You can now create JDBC type of CDATA Connector in Adeptia Connect. Click here for more information.  

Bug Fixes

  • The Process Flow that used a Text Layout took longer than expected to process large text files.

  • After AIS to AC migration, the ProcessFlowDescription variable failed to override the Process Flow descriptions as viewed on the Dashboard.

  • When users viewed the Acknowledgement details of an EDI Transaction (X12 Interchange) on the Dashboard > Transactions > Action > Acknowledgement page, it displayed a blank screen with no content.

  • Sometimes users were not able to view all the child Process Flows on the the Dashboard > Transactions manage page if the Process Flow had a large number of child Process Flows. 

  • Sometimes it took longer than expected to load a mapping in the data mapper and the page became unresponsive.

  • The list of Stored Procedure failed to populate in the Select Stored Procedure field (while creating a Stored Procedure) when there was a large number of Stored Procedures to be loaded.

  • Users were unable to create an Advanced Database Layout using an MS Access database that contained special characters or space in its table or column name.

  • In a rare scenario, a Transaction or Process Flow remained queued without ever going into the running state in the future.

Items included from the minor releases of AC v4.3 and AC v4.2​

The following sections mention the features and improvements, security enhancements, and bug fixes from the intermediate AC v4.2.x.x, AC v4.2.x.x.x and AC v4.3.x releases that have been merged with this release.

Adeptia Connect v4.3.x​

Adeptia Connect AC v4.3.x release includes the following new feature and bug fixes.

New feature

  • The application now supports the execution of an EDIFACT Inbound Transaction even when the source file has UNG segment defined in it. Also, you now have the option to have UNG segment in the Target file generated after the execution of the respective EDIFACT Outbound Transaction. To do so, select the Generate Group Header checkbox while creating the EDI Outbound Transaction.

    Warning In case the source file has UNG segment in it, the EDIFACT Inbound Transaction that matches the sender and receiver Id defined in the UNG segment is executed.

Bug fixes

  • Adeptia Connect was not able to connect to specific mail servers.
  • The Transaction created with a Data Integration Template was getting aborted when the Transaction had Post Process as the destination  
  • The Transaction got aborted when it used a Data Integration Template and had Post Process at the destination.
  • The Transaction > More Action > Event Status page displayed an incorrect number of associated Transactions.
  • View Dependencies option (under the More Action Menu) for some of the Events did not fetch and display the relevant details.
  • After upgrading to AC v4.3.01, all the Event type of activities stopped working.
  • Users were unable to view error records for EDI Transactions when the error pertained to a record exceeding the Max Rows limit (999). This has been fixed by removing the max rows limit and providing an option to view the erroneous record using the Status field.

Adeptia Connect v4.2.3.x​

Adeptia Connect AC v4.2.3.x release includes the following bug fixes.

Bug fixes

  • Some of the Process Flows were getting aborted with the error “Too few bytes for IV in input stream” when there was a large number of Process Flows to be executed.
  • The application performance slowed down when GitHub versioning was enabled and there was a large number of activities' check-ins.  

Adeptia Connect v4.2.3.1.x​

Adeptia Connect AC v4.2.3.1.x release includes the following bug fixes.

Bug fixes

  • Adeptia Connect now supports the following features in a Template/Transaction when you use Amazon S3 at Source:
    • Trigger in Sequence
    • Delete On Success
  • Sometimes, the application processed a newly added or updated file for two times consecutively.

Adeptia Connect v4.2.6.x​

Adeptia Connect AC v4.3.x release includes the following new features and bug fixes.

New features

  • New indexes have been added to improve the query execution on the log database.

  • The archival and cleanup utility has now been improved to ensure that all the logs are cleaned up when it runs.

  • The application now provides additional information about the logs that may have not been cleaned during the archival and cleanup operation.

    WarningTo get additional information about the logs, you need to set the value for the property logging.level.system (In the Account > Settings > Microservice Settings > ArchivalAndCleanup > Logging section) to INFO. The default value for this property is NOTICE.

  • The Advanced Search feature on the Dashboard > Transactions manage page has now been optimised further to fetch the results faster.

  • You can now compress multiple files coming from different sources in a Process Flow. This can be achieved by entering the names of the files in the FileName field, using a comma-separated format, within the Compression activity used in the Process Flow.

  • Adeptia Connect now enables you to mitigate any possibility of slow performance of the REST Consumer. This can be achieved by selecting the Use HTTP Client checkbox while creating a REST Consumer. For more details refer to this page. 

  • Adeptia Connect now provides an option to configure the Readiness Probe Criteria for a dedicated deployment. For more details refer to this page.

Bug fixes

  • In case the users had a primary and secondary environment, they were getting the prompt to activate the license after restarting the license microservice.

  • Sometimes the Process Flow with REST Consumer activity failed to execute with the error, Illegal character(s) in message header value: Bearer…, when the REST Consumer used OAuth authentication.

    WarningAfter upgrade, if you encounter this error with any existing REST Consumer that uses OAuth authentication, you need to create a new OAuth Account for it.

  • The REST Consumer (with HTTP Client enabled) execution in a Process Flow got stuck when the status code was 4xx and the error stream was NULL in response to the REST Consumer.

  • The value for DD_TAGS variable in the runtime deployment was getting overridden by the value for the envName variable defined in the values.yaml file.

  • Deactivating a dedicated deployment from the primary environment also changed its status as deactivated in the secondary environment although deployment pods continued to run in the secondary environment.
    This has been fixed by introducing the environment variable envName in the global > config section in global values.yaml file. Using this variable you can define the name of an environment. Deploying the application in primary and secondary environments after
    defining this variable in all the environments prevents the cascading effect of
    deactivating or activating a deployment across the environments.

  • The activities were not able to fetch the secrets from HashiCorp Vault when short lived tokens were used.
    This has been fixed by introducing the environment variable HASHICORP_VAULT_TOKEN_TYPE in the global > configManagement > backend > hashicorp section. The possible values for this variable are batch and service, and the default value is batch.  

  • While a Database Info (being used in a Mapping) in any of the Projects failed to fetch its secrets from the HashiCorp Vault and threw an error in the Debugger, another Database Info in another Project encountered the same issue even when it did not use Vault for fetching the secrets.

  • The abort behavior of a REST Consumer executed using HTTP Client was different from that of executing the same REST Consumer using Jersey.

  • Users were unable to view the archived log details of a Process Flow on the Dashboard > Transaction manage page if the Process Flow had more than 20 child process flows.

  • An Application Event was showing in activated state even when the Event was deactivated by the user.

  • The Child Process Flow got executed on the shared runtime pod instead of the dedicated runtime pod when the Parent Process Flow was called via REST or SOAP Web Service and the “Recoverable Process Flow” property was disabled.

  • The Positional Layout parsed Data Header as a record at runtime even when the Layout was configured to skip Data Header for processing.

  • The Process Flow failed to execute when the users used a Context Target activity in it and selected the Filter Empty Elements checkbox in mapping.

  • The REST Consumer configured to run in HTTP mode failed to execute when the value for the endpoint URL defined in the Consumer was set to be dynamic.

  • Users were sometimes not able to turn off a dedicated runtime Deployment.

  • The child Process Flows nested at level three and onwards got executed on the shared runtime deployment instead of the dedicated runtime deployment.

Adeptia Connect v4.2.6.3.x​

Adeptia Connect AC v4.2.6.3.x release includes the following new features and bug fixes.

New feature

  • While creating a Partner, you can now add the Partner’s phone number in the EDI Configurations section.  

    This also applies if you want to add multiple partners in one go using a CSV file.

    WarningYou can download the sample CSV file by following the link on the Import Partners window.
    To go to the Import Partners window, click Partners > Partners > Import Partner and follow the link "Click here to download sample file...". Once you download the file, you can add the partners' phone numbers and other details in the respective columns therein based on your requirements.

  • You can now change the EDI Partner associated with a Non- EDI Relationship by following the steps given below:

    1. Click Configure > Others. 
    2. Select either Non- EDI Inbound Relationship or Non- EDI Outbound Relationship from the list of activities based on you requirement. 
    3. Click Action > Update Partner against the required relationship.
    4. On the Update Partner screen, select the required Partner.  

Bug fixes

  • SAML users once logged into the application were unable to logout.
  • Sometimes Data Mapper screen got stuck when the user attempted to edit a mapping.
  • After AIS to AC migration, some of the Process Flows failed to execute and threw an error "Unable to map source data to target schema format".
  • When a mapping contained empty fields in the source file, the debugger mode displayed 'undefined' for the corresponding fields in both the Source and Target layouts.
  • After AIS to AC migration, the ProcessFlowDescription variable failed to override the Process Flow descriptions as viewed on the Dashboard.
  • Users were not able to opt for the On Local Disk option while editing a SOAP Consumer that had Over HTTP option selected in the WSDL Input field.
  • When a Layout containing similar namespaces with different namespace prefixes was migrated from AIS to AC, invalid clones on the root nodes were created in the associated Mapping.
  •  Sometimes Data Mapper screen got stuck when the user attempted to edit a mapping.
  • After migrating from AIS to AC, users were unable to Test the Source and Layout activities, and Save the Target activities.

Adeptia Connect v4.2.7.x​

Adeptia Connect AC v4.2.7.x release includes the following new feature and bug fixes.

New feature

  • Adeptia has now optimized the logic for displaying log cleanup status to IT users via UI notification.

Bug fixes​

  • When a process flow was executed using a REST Provider, the Dashboard > Transactions page showed the name of the owner of the REST Provider activity instead of the one who executed it.

    This has been addressed by introducing two configurable properties, abpm.ws.session.auth.enable and abpm.ws.session.token.location, to allow the users to execute a process flow based on the session token authentication.

    To configure these properties based on your requirement, you can access them by navigating to,
    **Account > Settings>Microservice>RESTAPIService
    **
    Given below are the details of the properties:

    • abpm.ws.session.auth.enable – Set this property to yes for session token authentication. On setting the value to no, process flow is executed by the owner of REST provider activity.

    • abpm.ws.session.token.location –

      • Set the value for this property to cookie if you have provided the Key as Cookie, Value as “ACCESS_TOKEN=”, and Style as Header in the REST client.

        WarningIf you are using a Web Form for executing the process flow, set the value for this property to cookie.

      • Set the value for this property to Header if you have provided the Key as ACCESS_TOKEN, Value as the access token, and Style as Header in the REST client.

  • The REST call made through invokeREST method within the Data Mapper failed to consume a REST endpoint when the endpoint had Client Authentication enabled.
    This has been addressed by enabling the users to define a security policy in the invokeREST method in either of the following ways:

    • You may add the security policy id as a query parameter in the endpoint URL using the given format,
      java:MapperUtilityClass.invokeREST(https://<domain>/endpoint?securityPolicyId=<Id>,'' ,'' ,'' ,'' , '','' ,'', '')
    • You can also add the security policy id as a QueryParam argument in the given format,
      java:MapperUtilityClass.invokeREST('https:// <domain>/endpoint,'','' ,'' ,'' , ' securityPolicyId=<Id>'','','')
      For more details refer to this page. 

  • An incorrect endpoint URL was depicted for an existing Rest Provider (migrated from AIS to AC4.x). 

  • Users were unable to save an existing (migrated from AIS to AC4.x) Advanced Database Layout after they added a WHERE clause in the Query field in the Layout.

  • The Data Mapper saved a mapping activity that used a Key Function even when the key was missing. 

  • The associated process flow failed to execute when an LDAP IT User triggered a Calendar Event using the Trigger Now option.

  • The Dashboard > Trigger screen did not show the Event logs for Process flows and Transactions.

  • The Key Function being used in a mapping could not get imported to another mapping that has the same Source and Target as that in the former one.

  • The Process Flows & Triggers section in Dashboard > Overview did not show the number of Process Flows that were in queued state.

  • The logs did not contain the required details about the misfired events.

  • The Search box in the Dashboard > System Logs page did not render properly.

  • The Mapping failed to load when it contained a large number of stored procedures.

  • When the users imported a Mapping, it failed to import the namespace and threw an error.

  • When there was a large number of active Events, the Tools > Maintenance > Scheduler page got unresponsive.

  • The users were unable to clean the Logs and archived Repositories using the ArchivalAndCleanup property.

  • The Process Flows section on the Dashboard > Overview > Process Flows & Triggers tab did not display the queued count (graph) for the Process Flows bound with a Calendar Event.

  • When the users had a large number of DB info activities, a mapping using a DB query was taking longer than expected to process.

  • The users were not able to save a Mapping that used a Value Map containing more than 1000 value mappings.

Application package location​

Adeptia Connect application (AC v4.3.x) is available as a Helm package in the ArtifactHUB. The migration Helm and roles zip also reside at ArtifactHUB. Here are their respective locations.

**https://artifacthub.io/packages/helm/adeptia-connect/adeptia-connect (artifacthub.io)
**

https://artifacthub.io/packages/helm/adeptia-connect-migration/migration (artifacthub.io)

https://artifacthub.io/packages/helm/adeptia-connect-roles/roles (artifacthub.io)

SuccessFor the Helm package of other versions, select the appropriate version from the CHART VERSIONS section of the respective package in ArtifactHUB. 

To know about how to install the application using the Helm package, click here. 

AC v4.3 documentation ​

You can visit the AC v4.3 documentation for detailed information on the application architecture, deployment, implementation, maintenance, and anything that you want to know about the application.