Skip to main content
Version: 4

AC v4.3 release highlights

New features and improvements​

  • **Document (OAS 3.0) based connector framework
    **The pre-built app connectors listed below now use document (OAS 3.0) based framework. You can also create a custom app connector in Adeptia Connect using this framework. To learn more, refer to the section App connectors.

    • QuickBooks
    • Xero
    • Dropbox
    • Google Drive
    • Salesforce

  • AC deployment with RabbitMQ in HA mode You can now deploy the Adeptia Connect application with RabbitMQ in HA mode. To learn more, refer to this page. 

  • Support for overriding an activity's configuration using the properties file in Git
    Adeptia Connect now enables you to override an activity's configuration using a Git repository at runtime. To learn more, refer to this page.

  • Comprehensive supports overriding an activity's secrets using HashiCorp Vault
    Adeptia Connect now enables you to override an activity's secrets using HashiCorp Vault at runtime. Click here for more information. 

  • Application licensing based on the total count of CPU cores configured 

    The application license now enforces the limit on CPU cores based on the total CPU cores configured for all the microservices together. Earlier the enforcement was based on the count of runtime microservice CPU cores. For more details, refer to this page.

    WarningBefore you upgrade to AC v4.3, ensure that you get the new license.

  • Improved usage report 
    You can now monitor the monthly usage by viewing the usage report. The usage report now also includes the following usage information:

    > Total number of Transactions or Process Flows executed. It includes both parent and child Process Flows.

    > Total volume of data received by all the sources, including the Web Service Consumers.

    > Total number of activities and actions executed in all the Process Flows and Transactions.
    For more details, refer to this page.

  • Support for AI-based Adeptia Assistant (chatbot) for Adeptia Connect help
    Adeptia Connect has integrated an AI chatbot, Adeptia Assistant, within the platform. This chatbot, serving as a virtual assistant, responds to user queries by deriving information from the Adeptia Connect help documentation. To learn more, refer to this page. 

  • Support for Retrieval Augmented Generation (RAG) to query your own knowledge base using ChatGPT 
    Adeptia Connect enables you to create your own knowledge base by uploading your content files and using an AI chatbot to query this knowledge base. To learn more, refer to this page.

  • Support for generative AI (ChatGPT) in AIMap for mapping suggestions
    Adeptia Connect has advanced its mapping suggestion functionality through the integration of generative AI, empowered by the GPT model. Click here for more information.

  • AI-based unstructured data processing support
    Adeptia Connect now provides a more efficient solution for converting your unstructured data (PDF or image files) into the structured data format of CSV or JSON by using the Extract Data template bundled with the application. To learn more , refer to this page.

  • UI Support for importing trust certificates to the application truststore 
    The certificates imported from Trusted Certificates screen as well as the ones bundled with the application are now stored in the application's truststore and are visible on the Trusted Certificates screen. For more details, refer to this section.

  • UI support for managing (edit, view, delete, and export) Trusted Certificate
    Adeptia Connect now enables you to View, Delete, and Export a certificate listed on the Trusted Certificates screen by using the More Action option against it. You can also export all the listed certificates using the Export All button. For more details, refer to this page. 

  • **UI support for uploading custom jar/class
    **Adeptia Connect now enables you to upload different types of custom classes and jars using UI. Click here for more information.

  • **Enhancement for configuring the HPA API version globally
    **You can now set the API version globally for all the HPA resources by setting the variable apiVersion under global > hpa in the global values.yaml file.

  • LAN file Source and Target accessibility from within the Kubernetes Cluster  Adeptia Connect now enables you to send and receive files from a Local Area Network (LAN) in the Kubernetes cluster environment. To learn more, refer to this page. 

  • Support for filtering individual activities based on their names for solution promotion    
    While creating an Export Package using Solution Promotion, you can now filter the individual activities to be included based on their names. To learn more, refer to this page. 

  • APIs to generate thread and heap dumps 
    You can now generate thread dump and heap dump of any pod in Adeptia Connect. Click here to learn more. 

  • **Support for creating a copy of the associated Event while copying a Transaction
    **While creating the copy of a Transaction, you now have the option to create a copy of the Event associated with the Transaction being copied. For more details, refer to this page.  

  • Support for configuring webapp gateway timeout
    You can now configure the webapp gateway timeout by setting the variable SERVER_NETTY_CONNECTION-TIMEOUT in the global values.yaml file. The default value for this variable is 300000 (in milliseconds).

  • Support for AVRO type of files in Kafka Target 

    • The Kafka Target now also supports AVRO data format.
    • The Kafka Target now also supports Byte Array data format.

  • Support for creating multiselect combo type of Transaction parameter with dynamic values 
    You can now create a multiselect combo type of Transaction parameter and populate its values dynamically using a REST Consumer. Click here to learn more.

  • Execution view of the Transaction provides Transaction execution time information   The execution details (visible in Dashboard > Transactions > More) of a Transaction now also include the total time taken by a Transaction to execute. Click here for more information. 

  • Performance improvement in Advanced Database Target 

    While defining an Advanced Database Target, you now have the option to optimize the performance for processing of high volume of records by tuning the number of records that can be processed simultaneously. For more details, refer to this page. Click here to learn more. 

  • Support for bypassing SSL Verification for a REST Consumer 
    You can now configure a REST Consumer to skip the SSL verification during its execution. For more details, refer to this page.  

  • Support for creating Security Policies using APIs 
    You can now create Security Policies using APIs provided by Adeptia Connect. To learn more, refer to this page.  

  • Overr****ide Advanced Settings for a Transaction/Template 
    You can now set the Logging Level, Repository File Retention, and Activities Logging Retention for a Transaction/Template at runtime in Adeptia Connect. Click here for more information.  

  • Additional cron expression to define firing schedule for Events 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. Click here to learn more. The list of supported Events and Connector apps is as follows:​

    Supported Events

    • Database Event

    • FTP Event

    • File Event

    • Calendar Event

    Supported Connector apps

    • FTP

    • Database

    • LAN

    • Google Drive

    • DropBox

    • NetSuite

    • Azure Blob

    • Box

    • Amazon S3

    • Microsoft SharePoint

    • ServiceNow

    • Big Commerce

    • FreshBooks

    • HubSpot

    • Magento

    • QuickBooks

    • Xero

    • SageOne

    • Shopify

    • Concur

    • Salesforce

    • Zendesk

    • Zoho CRM

    • BambooHR

    • Google Spreadsheets

    • Amazon Redshift

    • Apache Cassandra

    • Dynamic CRM

    • Email

  • Support for special characters in the header of an Excel layout 
    An Excel layout now also supports parsing of an Excel file with special characters in the header of the layout. 

  • Support for defining the archive folder name for EDI file in a Transaction at runtime While creating an EDI Transaction you can use a context variable, $PARTNER_NAME$, to create the archive folder for the EDI file at runtime based on the Partner name. Click here for more details.

  • Bulk activation and deactivation of Transactions, Events, and Templates You can now choose to turn ON/OFF multiple Transactions, Events, and Templates from the list displayed on their manage page. Click here to learn more.

  • Improved Queue Management 
    Adeptia Connect now provides an intuitive user interface to view and maintain the runtime queues. It shows the details -- running, queued, and the total number

     of Process Flows and Transactions in the Queues and also enables you to take the following actions on the Queues.

    • View Messages
    • Clean Queue 
    • Search for a Queue 
    • Refresh the list containing the Queues
      For more details, refer to this page.

  • Additional user details in the payload in case of an external mapping validation The request payload now also contains the user details such as UserId, UserName, FirstName, Role, etc., when the user performs an external mapping validation through a REST Consumer in a Mapping. Click here to learn more. 

Security enhancements 

  • The version of jQuery in Adeptia Connect has now been upgraded from v3.5.0 to v3.7.0 to remove critical and high vulnerabilities in it.

  • Business app certificates have been updated. 

  • Spring Boot and other libraries have been upgraded to fix critical and high vulnerabilities. 

Bug Fixes

  • In some cases, AIMap failed to provide mapping suggestions and threw a 504 Gateway Timeout error.

  • When the users upgraded from one AC v4.x to another AC v4.x environment, AIMap failed to provide mapping suggestions. This has been handled by changing the mechanism for encoding the AIMap-related properties' values.

    Success

    After upgrading to AC v4.3, set the values for the following properties to the values that you had in the older environment as they get reset to default values after the upgrade. You can set these properties by going to Account > Settings > Application Settings > Common.

    • app.jwt.key
    • app.jwt.issuer
    • app.jwt.expire.days
    • app.jwt.token.name
    • app.jwt.token.prefix.length
    • app.jwt.token.encryption.signature.algorithm
    • app.connect.jwt.token.expire.time
    • app.connect.jwt.token.expire.timeunit
    • app.connect.jwt.token.id.cookie.name
    • app.connect.jwt.ui.token.name

  • The system logged CPU utilization breach even when the actual utilization did not exceed the limit. 

  • The Process Flow using an Excel Layout got aborted when the users selected Optimize XLSX File Processing in the Layout.

  • While upgrading the environment, the license pod was sometimes throwing error and failed to get up and running.

  • The Process Flow using an Excel Layout got aborted when there were a large number of records to be processed. This has been fixed by adding the property abpm.schema.excel.poi.maxByteArray.size in Account > Settings > Microservice Settings > Runtime > Schema Property. The default value for this property is set to 100000000. You can set a value for this property based on the number of records you want to process. 

  • Allow Less Fields feature in a Positional Layout was not working as expected.

  • The Process Flow got aborted when the mapping used in it had Filter Empty Elements option checked.

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

  • Sometimes data mapper was getting failed with "Premature end of file error".

  • The Mapping threw an error when the XML file had the same URL for multiple namespaces. 

  • The Dashboard did not show the archived logs for the activities. 

  • The Order By clause was missing when the users opened the Advanced Database Source in edit mode.

  • When a Process Flow had a large number of child process flows associated with it, the Dashbaord failed to list them to show their details.

  • Advanced Text Layout was unable to parse the sample file when the record identifier in the file was within double quotes. 

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

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

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

  • For a Process Flow, the system created a repository file (0 kb) even when Generate Stream for activities such as Database target, Advanced Database target, and Custom Plugin was disabled. This also held true in case of a Stored Procedure having Context Parameters as the value for the Output Mode field.

  • The Transactions that used BambooHR Connector as a Source failed to execute when the user (API key used in the Connector) had permission to access the details of some employees but not others. This has been fixed by adding the property bamboohr.failOnNoAccessPermission located at **Settings > Application Settings > Connector > BambooHR.
    **

    Information
    • When the property is set to false, the details regarding the inaccessible data are logged in the Dashboard > Trigger > Logs with the relevant error message.
    • Setting this property to true prevents the user from processing the details of any employee if the user doesn’t have access to even a single employee in BambooHR.

  • File Event picked the files (with VFS enabled) from all the sub-folders even when it was configured to pick them up from a specific location.

  • The system did not generate logs for the FTP Target (with SFTP protocol) after the execution of the Process Flow that used this Target.

  • After upgrading to AC v3.7.2, users encountered an error while attempting to log in to Adeptia Connect using the IDP Initiated SSO URL.

  • The application sometimes threw the error "Archival is not enabled" during the log cleanup and archival process.

  • After upgrading from Adeptia Connect v3.7.1 to v3.7.2, the Process Flows having a Gateway condition that used a script failed to execute without throwing any error.

    WarningAfter applying the patch, you need to open the Process Flow in edit mode and save it before executing. 

  • The users were getting an error when they tried to access the GitHub repository through proxy. 

  • The System Console showed incorrect dates for the failed log cleanup and archival execution.

  • The Sub-element Separator defined in the ISA Envelope was getting replaced by a whitespace in the output file generated after the execution of the EDI X12 Outbound Transaction.

  • The value of the header sent in the request of a REST Provider was always set in small case in the Context Info, leading to the failure of the associated Process flow’s execution.

  • Users were getting 404 error when they used a REST Consumer to hit a Snowflake's REST API via a proxy.

  • When a SOAP Consumer used in a Process Flow encountered an error, no activity next to it could be executed.

  • When the Agency Code under the UNH segment in the Source file was not defined, the generated acknowledgment file contained : (colon) in the UCM segment.

  • The Adeptia Connect application was not able to generate reconcile acknowledgement against an outbound EIDFACT file.

  •  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.

  •  In case of multiple EDI Outbound Transactions (with Content Based Routing enabled) using the same Event, the execution of the Transactions failed when the Source Layout and the Mapping for the Transactions was updated.

    WarningIt is recommended that you update the Source Layout and the Mapping for all the Transactions.

  • While creating an FTP Target, the screen got stuck when the user attempted to test the connection with the FTP server. 

  • In case of multiple process flows bound with an Event that has Trigger in Sequence option checked did not result in sequential execution of process flows and one of the process flows got stuck in the queue.   

  • An FTP activity was not able to establish connection with the SFTP server using the new algorithm.

  • Sometimes the Process Flow was getting stuck when the associated event had Trigger in Sequence checked.  

  • Sometimes the Partners tab > Partners > More action > Transaction page did not show all the Transactions associated with the Partner being searched for.

  • When users searched for Transactions with a specific keyword, the total count of active Transactions listed on the Trigger section differed from that shown on the Transaction page. 

Items included from AC v4.2.x releases​

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

Adeptia Connect v4.2.1​

Adeptia releases the version, AC v4.2.1, which includes the following new features and bug fixes.

New feature

  • The values for the following properties of the Azure Service Bus target in a process flow can now be set or overridden at runtime. 

    • Correlation ID

    • Message ID

    • Label/Subject

    • Reply To

    • To

    • Session ID

      To set or override the values at runtime, do the following:

      1. In the Process Flow, open the Activity Properties panel for the Azure Service Bus target.
      2. Select VARIABLES, and then Input.
      3. Select Activity as Type.
      4. In the Name field, select the property whose value you want to set or override.
      5. In the Value field, enter the value for the field you selected in step 4. 
      6. Click Add.

  • You can now replace an existing Azure Service Bus (ASB) target with another ASB target in a Process Flow at runtime. To do this,

    1. In the Process Flow, open the Activity Properties panel for the Azure Service Bus target.
    2. Select VARIABLES, and then Input.
    3. Select Activity as Type.
    4. In the Name field, select TypedId.
    5. In the Value field, enter the Typed Id of the ASB target you want to use with the Process Flow. 
    6. Click Add.

  • In an Azure Service Bus listener, you now have the option to process all the messages irrespective of their Session IDs. For more details on Azure Service Bus listener, click here.

Bug fixes

  • Users were not able to connect to the Oracle database (used as the Backend, Log, Quartz, and Log archive database) using Kerberos authentication. To ensure a successful connection, follow the details given here.
  • Users were unable to connect to the Source or Target database when the Database Info activity used in them was configured to use Kerberos authentication. To ensure a successful connection, follow the details given here.
  • For a Process Flow, the system created repository file (0 kb) even when Generate Stream for activities such as Database target, Advanced Database target, and Custom Plugin was disabled. This also held true in case of a Stored Procedure having Context Parameters as the value for the Output Mode field. This has now been fixed for Process Flow's runtime execution as well.

Adeptia Connect v4.2.2​

Adeptia releases the version, AC v4.2.2, which includes the following new features and bug fixes.

New feature

  • Support for Kerberos authentication for the Backend and Log database in AIMap.

Bug fixes

  • krb5.conf file path was not getting set properly in microservices.
  • Kerberos configuration information was not getting set properly in runtime deployment.
  • After changing the logging level to Debug, the Event service failed to resume.
  • Users were not able to use the APIs for the System Console following the instructions given in the documentation. 
  • Users were getting error when they used Hikari as the Connection Pool in Database Info activity.
  • Adeptia Connect UI was frequently getting stuck when Kerberos authentication was used for Backend and Log Databases.

Adeptia Connect v4.2.3​

Adeptia releases the version, AC v4.2.3, which includes the following new features and bug fixes.

New features

  • 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. Additionally, you can now perform the following actions in an Advanced Text Layout created/edited using the default method or the Layout Builder.

    • Specify a field that you want to use as the record identifier in an Advanced Text Layout. 
    • Ignore a record that does not hold any value in any of its fields, including the record identifier. 

  • In case of using Ingress, the application now uses port 443 for accessing REST provider endpoints. This could be achieved by adding an environment variable DEFAULT_SERVICE_PORT with 443 as its value in the global values.yaml file.

  • In addition to the number of running pods of runtime (both shared and dedicated deployments) microservice, you can now also see the following information about runtime pods execution on the application’s System Console > Report screen.

    • Concurrency
    • Number of Transactions/Process Flows in running state
    • Number of Transactions/Process Flows in queued state

Bug fixes

  • The partner users were not able to select an Advanced Database Source in a Transaction.

  • The response had the status code "200" even when there was an error while copying a Mapping or Layout using API.

  • Users were unable to create an Oauth Account using an Oauth Profile that had a rather long Client Id or Client Secret used in it.

  • Azure Blob Event was fetching all the types of files even when it was configured to search for only specific types of files, for example, .txt.

  • The Logs Clean-up screen (Under Account > Tools > Maintenance) was not getting loaded. This has been fixed, however, the users will not be able to see the repository file size on this screen for now.

  • Users were not getting relevant error message when the following layouts were used for parsing the files larger than 100KB in size.

    • Text
    • Advance Text
    • Advance Positional
    • Positional

  • In case of using the following layouts, the users encountered an error when they clicked inside a blank subfield of an array field.

    • Text

    • Advance Text

    • Advance Positional

    • Positional

  • While uploading a file containing array data to the following layouts, the users encountered an error “Uploaded file is not in correct format” if a subfield’s name of an array field contained spaces.

    • Text
    • Advance Text

Adeptia Connect v4.2.4​

Adeptia releases the version, AC v4.2.4, which includes the following new features and bug fixes.

New features

Bug fixes

  • Users were not able to upload a file of more than four MB size to the Azure Blob Target.

  • The dashboard did not show the queued Process Flows that were bound with a JMS Event.

  • Testing of an Azure Service Bus account failed in case the users did not have Manage, Listen, and Send permissions on Azure Portal.

  • The Deployments Information screen that appears by going to System Console > Report > Runtime (Process Execution) > View displayed incorrect information about a dedicated deployment in case another deployment with a similar name existed.

  • The messages were not getting processed concurrently when the Process All Sessions was enabled in an Azure Service Bus Listener. This has been fixed by introducing Max Concurrent Sessions and Max Concurrent Calls parameters. For more details, refer to this page.

  • The SAML users were not able to view and edit any of the following activities from within the Web Process Designer:

    • Application Source

    • Application Target

    • Azure Service Bus Target

    • and Stored Procedure

  • Some Process Flows were getting aborted with Header not found error when a large number of Azure Blob files were being processed. 

  • The custom IT users (company only type) were not able to view the queued Process Flows on the Dashboard.

Changes in roles zip file

There is no change in the roles.tgz (roles zip) file for this release.

Changes in values.yaml file

The values.yaml file for AC v4.2.4 has got changes when compared to that for AC v4.2.3. For more details, refer to this page.

Adeptia Connect v4.2.5​

Adeptia releases the version, AC v4.2.5, which includes the following new features and bug fixes.

New features

  • You can now enable database connection leak detection mechanism in the application by using the following environment variables in values.yaml file. By default, the database connection leak detection is disabled as these variables are set to 0 (zero). To enable it, set a time (in milliseconds) as the value for these variables. 

    • BACKEND_LEAK_DETECTION_THRESHOLD 
    • LOG_LEAK_DETECTION_THRESHOLD
    • LOG_ARCHIVE_LEAK_DETECTION_THRESHOLD
    • QUARTZ_LEAK_DETECTION_THRESHOLD

  • Readiness probe has been optimized to prevent the pods from going into non-ready mode.

Bug fixes

  • Azure Service Bus Listener failed to consume a message sent with a delay of 10 minutes or more. The following configurable parameters have been introduced for the Azure Service Bus Listener activity to address this issue.

    • Max Auto Lock Renew Duration: The maximum duration (in minutes) for automatically renewing a lock on a message during message processing.
    • Session Timeout**:** The maximum duration (in hours) for which the Azure Service Bus Listener will keep checking for the message. If no message is received during this period, the session gets timed out and the listener will not process any message further. 
    • Max Retries: The maximum number of attempts made by the Azure Service Bus Listener to check for new messages.
    • Retry Delay: The frequency (in seconds) at which the Azure Service Bus Listener checks for a new message.
    • Retry Mode: Defines if the value for the Retry Delay field is fixed or exponential in nature.
      • Fixed: Azure Service Bus checks for a new message at a fixed interval (value provided in Retry Delay field).
      • Exponential: Refers to the exponential increase in message checking frequency at every attempt. This increase is calculated as Retry Delay * Max Retries.
    • Max Retry Delay: The maximum permissible delay between message checking attempts.

  • The following jars went missing from the /shared/customClasses folder during the application upgrade.

    • DataInterfaceUtils.jar
    • EDIUtils.jar
    • MapperUtility.jar

Adeptia Connect v4.2.6​

Adeptia releases the version, AC v4.2.6, which includes the following bug fixes.

Bug fixes

  • After switching from the primary to the secondary region, the JMS messages were getting processed on the primary region even when the Scheduler in the primary region was paused.
  • The AUTOSCALING file got deleted on the deletion of a dedicated Queue.
  • The Runtime deployment manager created multiple replica sets due to high CPU usage.
  • There was a Datadog service tag label mismatch for dedicated Runtime deployments.
  • In some cases, AIMap failed to provide mapping suggestions and threw 504 Gateway Timeout error.
  • 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.
  • When users created a Transaction/Template using FTP as the source application, the On File Exists event trigger type was unavailable for selection.
  • Users were getting an error when they clicked Success or Error links (to see the successful or failed Transactions) in Non EDI and EDI tabs on the Dashboard's Overview screen.
  • On deleting the copy of an EDI Transaction, the FTP Target set at the destination of the original Transaction got removed.
  • Users were getting an error when they tried to see the list of Custom, Convert, DI, EDI, and Pass-Thru Transactions by clicking their corresponding links available below the donut chart on the Transactions manage page.
  • The application showed the Adeptia Connect home page before it loaded the form for creating the application Source or Target in Web PD.
  • The Acknowledgements section on the Dashboard > Overview > EDI tab did not show any entries for the executed EDI Transactions (with Expect Acknowledgement set to Yes).
  • The Acknowledgements, Inbound Transactions, and Outbound Transactions sections on the Dashboard > Overview > EDI tab did not show any entries for the executed EDI Transactions (with Expect Acknowledgement set to Yes).
  • The Top 5 Partners By Volume and Top 5 Message Types By Volume sections on the Dashboard > Overview > EDI tab did not show any entries for the successfully executed EDI Transactions.

Changes in values.yaml file

The values.yaml file for AC v4.2.6 has got changes when compared to that for AC v4.2.5. The default value for the CPU limits and CPU requests in the runtimedeploymentmanager section has been changed to 1500m and 300m respectively, as shown in the following screenshot.

Adeptia Connect v4.2.6.1​

Adeptia releases the version, AC v4.2.6.1, which includes the following bug fixes.

New features

  • All the microservices now support Kerberos authentication.

Bug fixes

  • When the Listener Microservices was restarted, the IT Users were unable to access the logs for a Process Flow that used an ASB Listener.
  • During execution, the Process Flow/Transaction continued using the previously configured connection pool set in the DB Info even when the database connection pool was changed.
  • The dedicated Runtime deployments failed to parse the application name defined in the DD_TAGS environment variable in the values.yaml file.

Changes in values.yaml file

  • The following environment variables have been added to the global > environmentVariables section in values.yaml file.

    Environment variable
    		Default value
    BACKEND_ABANDONED_CONNECTION_TIMEOUT10
    BACKEND_INACTIVE_CONNECTION_TIMEOUT60
    BACKEND_QUERY_TIMEOUT60
    BACKEND_FAST_CONNECTION_FAILOVER_ENABLEDtrue
    LOG_ARCHIVE_ABANDONED_CONNECTION_TIMEOUT10
    LOG_ARCHIVE_INACTIVE_CONNECTION_TIMEOUT60
    LOG_ARCHIVE_QUERY_TIMEOUT60
    LOG_ARCHIVE_FAST_CONNECTION_FAILOVER_ENABLEDtrue
    LOG_ABANDONED_CONNECTION_TIMEOUT10
    LOG_INACTIVE_CONNECTION_TIMEOUT60
    LOG_QUERY_TIMEOUT60
    LOG_FAST_CONNECTION_FAILOVER_ENABLEDtrue
    QUARTZ_ABANDONED_CONNECTION_TIMEOUT10
    QUARTZ_INACTIVE_CONNECTION_TIMEOUT60
    QUARTZ_QUERY_TIMEOUT60
    QUARTZ_FAST_CONNECTION_FAILOVER_ENABLEDtrue

Adeptia Connect v4.2.6.3​

Adeptia releases the version, AC v4.2.6.3, which includes the following enhancements and bug fix.

New features

  • The runAsNonRoot parameter has now been defined at the container level.
  • A non-root user has now been bundled with each docker image. This enables only the bundled user to run the processes in the application.
  • The DD_PROXY_NO_PROXY tag has been to all the deployments to send traces related to proxy to datadog.
  • You can now configure the Git proxy by following the steps given below.

  1. Open the deployment file of webrunner.

  2. Add -Djdk.http.auth.tunneling.disabledSchemes="" to the JAVA_OPTS variable.

  3. Log in to the Adeptia Connect.

  4. Click Account > Settings.

  5. Expand Miroservice Settings in the left panel.

  6. Select WebRunner.

  7. Expand Version Control.

  8. Update the properties described in the following table.

    Property
    		Description

    abpm.versionControl.proxy.enable

    		Provide the value as true to enable the proxy server to access the version control system.

    abpm.versionControl.proxy.host

    		Provide the host name of the proxy server.

    abpm.versionControl.proxy.port

    		Provide the port number of the proxy server.

    abpm.versionControl.proxy.username

    		Provide the username for the proxy server.

    abpm.versionControl.proxy.password

    		Provide the password for the proxy server.

Bug fix

  • The runtime pods failed to come up and running as the following environment variables for runtime were not getting set at the time of deployment.
    • BACKEND_KERBEROS_CONFIGURATION
    • LOG_DB_KERBEROS_CONFIGURATION

Adeptia Connect v4.2.6.4​

Adeptia releases the version, AC v4.2.6.4, which includes the following enhancements and bug fix.

New features

  • The Azure Service Bus Listener in Adeptia Connect now also supports the processing of a message with body type as VALUE and SEQUENCE. 

Bug fix

  • The values set for the following environment variables at the time of deployment were not reflected at runtime.
    • BACKEND_DB_MAX_ACTIVE
    • LOG_DB_MAX_ACTIVE
    • BACKEND_DB_MIN_IDLE
    • LOG_DB_MIN_IDLE

Adeptia Connect v4.2.6.5​

Adeptia releases the version, AC v4.2.6.5, which includes the following enhancements and bug fixes.

Bug fix

  • An error message, "Error during Kerberos5 authentication", got logged in the runtime pod’s log, even though the Kerberos authentication was not used for backend or log databases.
  • The Spawn Process Flow got executed on the shared runtime pod instead of the dedicated runtime pod when the “Recoverable Process Flow” property was disabled for the Parent Process Flow.
  • In case two Webrunner pods were running and the user updated the File Base Location field of an Event activity, it still showed the older file path.

Adeptia Connect v4.2.6.6​

Adeptia releases the version, AC v4.2.6.6, which includes the following enhancement and bug fix.

Enhancement

  • Performance improvement in parallel execution of the process flows.

Bug fix

  • Sometimes data mapper was getting failed with "Premature end of file error".

Adeptia Connect v4.2.6.6.1​

Adeptia releases the version, AC v4.2.6.6, which includes the following enhancement.

Enhancement 

  • You can now create a new file that can be read by the runtime deployment manager to launch a deployment based on the entries defined therein. The default file in the AC application to serve this purpose is AUTOSCALING. Creating a new file is useful when the default AUTOSCALING file gets corrupted. To create a new file, do the following:
    1. Open the AC v4.2.6.6.1 values.yaml file.
    2. In the environment variable autoscalingFile, enter a name for the new file, for example, NEW_AUTOSCALING.
    3. Save the file.
    4. Upgrade to AC v4.2.6.6.1.

Adeptia Connect v4.2.6.8​

Adeptia releases the version, AC v4.2.6.8, which includes the following enhancements.

Enhancements 

  • You can now define a gateway condition in a Process Flow by using Spring Beans.

  • While defining an Advanced Database Target, you now have the option to optimize the processing of high volume of records by specifying the number of records that the Queue can hold at a time. For more details, refer to this page. For more details, refer to this page.

Adeptia Connect v4.2.6.9​

Adeptia releases the version, AC v4.2.6.9, which includes the following enhancements and bug fixes.

**Enhancements
**

  • You can now create a new file that can be read by the runtime deployment manger to launch a deployment based on the entries defined therein. The default file in the AC application to serve this purpose is AUTOSCALING. Creating a new file is useful when the default AUTOSCALING file gets corrupted. To create a new file, do the following:

    1. Open the AC v4.2.6.9 values.yaml file.
    2. In the environment variable autoscalingFile, enter a name for the new file, for example, NEW_AUTOSCALING.
    3. Save the file.
    4. Upgrade to AC v4.2.6.9.

  • You may sometimes get an error while trying to activate a JMS Event that is shown in the deactivated (OFF) state on the Events manage page. This may occur if the JMS Server goes down and at the same time, the Adeptia Connect Event microservice also gets restarted. This leads to a change in the status of the JMS Event as deactivated (OFF) in the UI.

    This has been addressed by introducing two properties, abpm.event.startup.activation.retryCount and abpm.event.startup.activation.retryInterval, to enable the Event microservice to retry the connection with the JMS Server for a specific number of times at specific intervals.

    In case you want to configure these properties based on your requirement, you can access them by navigating to  Account > Settings > Common > Event.
    Given below are the details of the properties: 

    Property name 
    		Description 
    		Default value 
    abpm.event.startup.activation.retryCount
    		The number of times the Event microservice will try to re-establish the connection. 
    		3
    abpm.event.startup.activation.retryInterval
    		The time interval at which the Event microservice will try to re-establish the connection. 
    		5
    Warning
    • In case the Event microservice fails to re-establish a connection, an email is sent to the System Admin.
    • Once the Event is deactivated (both on the UI and in the database), the Message Centre on the Application UI notifies a relevant message.

  • The runAsNonRoot parameter has now been defined at RabbitMQ container level.

Bug fixes

  • Users were unable to log in to the application when there were more than one portal nodes in the environment and SAML authentication was enabled. This has been fixed by providing a variable, sessionAffinity, in the values.yaml file which can be configured by the user.

    To configure the variable, do the following:

    1. Open the AC v4.2.6.9 values.yaml file.

    2. In the Portal section, uncomment the sessionAffinity variable and provide the configurations.

    3. Save the file.

    4. Upgrade to 4.2.6.9.

  • The value of the header sent in the request of a REST Provider was always set in small case in the Context Info, leading to the failure of the associated Process flow’s execution.

  • The Process flow bound with a JMS Event that was created and activated by an IT user got executed first as the IT user and subsequently as an Admin user after the Event microservice was restarted.

Changes in values.yaml file​

  • The following environment variable has been added to the global > rabbitmq > securityContext > containerSecurityContext > securityContextFields section in values.yaml file. 

    VariableDefault value
    runAsNonRoottrue

  • The following environment variable has been added to the global > portal section in the values.yaml file. 

    VariableDefault value
    sessionAffinityConfigurations to be provided by the user

Adeptia Connect v4.2.6.10​

Adeptia releases the version, AC v4.2.6.10, which includes the following bug fix.

Bug fix

  • When the data length in the source file was smaller than the data length defined in the Positional Layout, the test and execution of the Positional Layout failed even though the Allow Less Fields option was selected.

Adeptia Connect v4.2.6.11​

Adeptia releases the version, AC v4.2.6.11, which includes the following enhancements and bug fixes.

Enhancements

  • 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 provides an option to configure the Readiness Probe Criteria for a dedicated deployment. For more details refer to this page.

Bug fixes

  • 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.12​

Adeptia releases the version, AC v4.2.6.12, which includes the following bug fixes.

Bug fixes

  • 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.

Adeptia Connect v4.2.7​

Adeptia releases the version, AC v4.2.7, which includes the following bug fixes.

New features

  • While editing an existing layout, you can now download the XSD, hierarchy XML, and the field file for the Layout based on your requirement. For more details, refer to this page.
  • Adeptia Connect now enables you to access and use a LAN file Source or Target from within the Kubernetes cluster. To achieve this, you need to create a PVC for the LAN file server by following the steps given on this page.
    This PVC mounts to the following microservices:
    • archival-and-cleanup
    • event
    • listener
    • portal
    • webrunner
    • runtime (dedicated & shared)
  • Adeptia Connect deployed through the Adeptia Connect Rancher package now helps you back up and restore the storage volumes by using Adeptia Connect Longhorn UI. For more details, refer to this page.
  • You can now mount an additional storage to the Kubernetes nodes to expand the schedulable storage for the application deployment using the Adeptia Connect Rancher package. For more details, refer to this page.
  • The users can now access the Kibana Dashboard only after successful authentication. For more details, refer to this page.
  • The Adeptia Connect Rancher package now performs the following pre-deployment checks:
    • Log and backend database connectivity
    • DNS domain of the Load Balancer
    • DNS domain for accessing the Adeptia Connect portal
    • Ports status (opened or closed) on the Load Balancer and the nodes 

Bug fixes

  • The users were not able to migrate AC v3.x objects to AC v4.x environment.
  • The users were getting an error message on the Web Process Designer when the stream generated from an activity was not being consumed.
  • When the user edited an EDI (837) Transaction, the option selected in the Transaction Set Code field on the EDI Configuration screen was removed and required a re-selection.
  • The users were getting an error message while updating the Project field (Under Advanced Properties) for the EDI Layout X12_005010X222A1_837.
  • A re-activated Transaction could not be executed using the run now feature.
  • The Success or Error links in the EDI tab on the Dashboard's Overview screen did not display the correct number of entries based on the selected time period of execution as either 7 or 30 days.
  • After migrating from AIS to AC v3.7, the Time Stamp format "mmddyyyy" was missing for the FTP Target being used in a Transaction.
  • The users were facing GUI issues while editing a Non-EDI Outbound Relationship that had more than 4000 FTP Target types to select from.
  • 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.
  • When the users tried to edit a Process Flow from within the Project manage page, they were getting redirected to the Edit Template screen.
  • AIMap was not able to provide suggestions for some of the similar fields in Source and Target.
  • AIMap suggested branch nodes to be mapped to the leaf nodes.
  • The Inbound and Outbound Acknowledgements section on the Dashboard > Overview > EDI tab did not show the complete list of EDI Partners.
  • The users were getting an error message even when an EDI Partner got successfully deleted from the Partners manage page.
  • The Acknowledgements section on the Dashboard > Overview > EDI tab did not show any entries for the executed EDI Transactions (with Expect Acknowledgement set to Yes).
  • The Acknowledgements, Inbound Transactions, and Outbound Transactions sections on the Dashboard > Overview > EDI tab did not show any entries for the executed EDI Transactions (with Expect Acknowledgement set to Yes).
  • The Top 5 Partners By Volume and Top 5 Message Types By Volume sections on the Dashboard > Overview > EDI tab did not show any entries for the successfully executed EDI Transactions.
  • The Acknowledgements section on the Dashboard > Overview > EDI tab showed an incorrect number of entries for the executed EDI Transactions (with Expect Acknowledgement set to Yes).
  • While moving activities from one Project to another, the activities that were not selected also got moved.
  • When the users upgraded to AC v4.2.5 or later, the existing ASB Listeners from the older versions threw a "NullPointerException" error on activation.
  • During execution, the Process Flow/Transaction continued using the previously configured connection pool set in the DB Info even when the database connection pool was changed.
  • The data was not displayed in EDI Message logs page for fields that were mapped and present in uploaded EDI Report File.
  • Some of the AC v4.x utilities (Webmapper, Webpd, and Custom Plugin) that were to use custom classes available in .../shared/customClasses folder did not run as expected.
  • The WSDL Layout being used at the destination of the mapping did not show all the fields/extensions.

Changes in roles zip file

The file nfs-pv.yaml has been added to the roles.tgz zip for this release to help you access and use a LAN file Source or Target from within the Kubernetes cluster. For more details, refer to this page.

Changes in values.yaml file

  • The following environment variables have been added to the global > environmentVariables section in values.yaml file.
VariableDefault value
BACKEND_ABANDONED_CONNECTION_TIMEOUT10
BACKEND_INACTIVE_CONNECTION_TIMEOUT60
BACKEND_QUERY_TIMEOUT60
BACKEND_FAST_CONNECTION_FAILOVER_ENABLEDtrue
LOG_ARCHIVE_ABANDONED_CONNECTION_TIMEOUT10
LOG_ARCHIVE_INACTIVE_CONNECTION_TIMEOUT60
LOG_ARCHIVE_QUERY_TIMEOUT60
LOG_ARCHIVE_FAST_CONNECTION_FAILOVER_ENABLEDtrue
LOG_ABANDONED_CONNECTION_TIMEOUT10
LOG_INACTIVE_CONNECTION_TIMEOUT60
LOG_QUERY_TIMEOUT60
LOG_FAST_CONNECTION_FAILOVER_ENABLEDtrue
QUARTZ_ABANDONED_CONNECTION_TIMEOUT10
QUARTZ_INACTIVE_CONNECTION_TIMEOUT60
QUARTZ_QUERY_TIMEOUT60
QUARTZ_FAST_CONNECTION_FAILOVER_ENABLEDtrue
  • The default value for USE_SUBJECT_CREDS_ONLY environment variable has been changed to true.
  • A lanVolumeConfiguration section under global > infra has been added to values.yaml file. You can configure the properties (highlighted in red in the following screenshot) in this section to access and use a LAN file Source or Target from within the Kubernetes cluster. For more details, refer to this page.
    C:\250b955f9e85115be18149877a8e9d0a

Adeptia Connect v4.2.7.3​

Adeptia releases the version, AC v4.2.7.3, which includes the following bug fixes.

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, the 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.

      WarningIn case the user does not have permission to execute the process flow, an error is logged even when the properties are configured to allow execution on the basis of session token authentication.

  • 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.

Items included from AC v4.2.9 through AC v4.2.24 releases​

The following section mentions the enhancements and bug fixes from AC v4.2.9 release through AC v4.2.24. 

Enhancements

  • You can now process the Inbound EDIFACT and EDI X12 file that use the same file Event.
  • Adeptia Connect now lets you export the logs for EDIFACT Interchanges and EDIFACT Messages from the Dashboard.
  • At the File Generation Policy step, while configuring the Destination for a Transaction, you can now select WINDOWS-1252 instead of manually entering it in the Data Encoding field.

Bug fixes

  • The system logged CPU utilization breach even when the actual utilization did not exceed the limit.

  • When the source EDI file contained multiple EDI Transaction types, for example, 997 and 850, the target file names on the EDI X12 Interchange Dashboard were shown the same for all the corresponding EDI Transactions types.

  • When multiple EDI Transactions ran simultaneously, the LAN File Target was sometimes getting aborted.

  • An EDI Transaction had different Started timestamp values on EDI X12 Interchanges and Transactions Dashboard. This resulted in the no-show of the same Transaction on one of the dashboards when searched for based on the timestamp.

  • The Outbound EDI Transaction was getting aborted when the source file it used had a delimiter present in it as part of the data. The application now replaces the delimiter, if it is present as part of the data in the source file, with a space in the target file.

  • For an Outbound EDI Transaction, the EDI X12 Interchanges dashboard displayed the date timestamp syntax as <Filename>_%%yyyyMMdd%%_73.%%yyyyMMddHHmmss%% for the generated target file instead of displaying the actual date-time value appended to the file name.

  • The acknowledgment status for an EDI Transaction was shown as No even when it was set to Yes with Error while configuring the Transaction.

  • In case of EDI inbound transaction, the target file was getting generated with .edi extension when the users did not define its file extension while creating the Transaction. 

  • The EDI transactions were sometimes getting aborted due to deadlock error in the log database.

  • When the users downloaded the EDI outbound file from EDI dashboard, the … was getting replaced by ?.

  • The event registry got deleted when the users deleted one of the multiple outbound Transactions that used the same Event.

  • When the users deleted one of the multiple inbound Transactions that used the same Event, all the other Transactions stopped processing the files.

  • In case of same Event being used by multiple inbound Transactions, the event kept processing the source files for a Transaction that was deactivated.

  • The Adeptia Connect application now helps you generate acknowledgement file against an inbound EIDFACT file.

  • The Adeptia Connect application now helps you generate reconcile acknowledgment against an outbound EIDFACT file.

  • The application now supports the generation of a separate UNB for each Transaction against an outbound EDIFACT file. You can achieve this while creating the Transaction by selecting the "UNB Generation Strategy" checkbox under "UNB Envelope Properties" at "EDI Configuration" step.

  • The license hard violation is now handled gracefully by the application.

  • In case two Webrunner pods were running and the user updated the File Base Location field of an Event activity, it still showed the older file path.

  • When an invalid inbound file was processed, the application executed the partner transactions that were not intended to be executed.

  • When two Transactions ran concurrently on different runtime pods, sometimes the target file generated first was getting replaced by the second one.

  • The View screen of an EDI Transaction showed "Compliance Check" as "Yes" even when the Compliance Check checkbox was not selected in the Transaction. Also, when the Compliance Check checkbox was selected, the View screen showed the "Compliance Check" as "No".

  • During log cleanup, some errors were being written in the log file.

  • The sender qualifier, receiver qualifier, and routing address were not getting written in the UCI segment of the generated acknowledgement file though they were
    present in the EDIFACT source file.

  • The EDI Outbound Transaction generated the files in UTF-8 encoding and the users did not have the option to configure it in the Transaction. This has been fixed by adding a configurable property Data Encoding. To generate the file in ANSI encoding, you need to set the value for this property to WINDOWS-1252 at the File Generation Policy step while configuring the Destination for the Transaction.
    C:\Users\ashhad.alam\Downloads\screen.PNG

  • The Dashboard (Action > Execution Details) did not show user friendly message for the failure of EDI Transactions in case the license did not support the EDI Transactions.

  • In case of multiple EDI Outbound Transactions (with Content Based Routing enabled) using the same Event and Source file, the execution of the Transactions ran in an endless loop.

  • When the Association Assign Code under the UNH segment in the Source file was not defined, the generated acknowledgement file contained : (colon) after UN in the UCM segment.

  • In case of an EDIFACT type of outbound EDI Transaction, the name of the data dictionary D07A was getting trimmed as D:7A in the generated target file.

  • In case of multiple EDI Outbound Transactions (with Content Based Routing enabled) using the same Event and Source file, the target file included the data of all the other partners. This happened in case of multiple identifiers in the Source file. Now, the application aborts such a Transaction with an error message.

  • The users were not able save the ISA Envelope when the value for the Interchange ReceiverID field had a space. This has been fixed for both the receiver and the sender Ids in ISA and UNB envelopes.

  • When the users downloaded the Target file generated after the execution of an EDI Transaction from EDI Interchange and Message logs page, an extra line was getting displayed in file.

  • When the Agency Code under the UNH segment in the Source file was not defined, the generated acknowledgment file contained : (colon) in the UCM segment.

  • In case of multiple EDI Outbound Transactions (with Content Based Routing enabled) using the same Event, the execution of the Transactions failed when the Source Layout and the Mapping for the Transactions was updated.

    WarningIt is recommended that you update the Source Layout and the Mapping for all the Transactions.

  • The execute_migration_job variable in the general-config.yaml is now set to false to prevent the deployment of accelerators during the upgrade that may override the changes you may have done in the bundled objects. It is recommended that you set the value for this variable to true while doing a fresh install.

  • The EDI Outbound Transactions were getting aborted when they were associated with the same event and had similar types of identifier values (Like HELLA, HELLA_EU, HELLA_EU_HER, HELLA_EU_BHTC, etc.).

  • Additional space was displayed in the inbound target Advanced Positional file when it was downloaded from the interchange page.

  • In ArchivalAndCleanup, the retain time for archival was not working properly.

  • The application did not support the special character . (dot) for the receiver Id and sender Id defined while creating the ISA Envelope, UNB Envelope, and Partner.

  • The Sub-element Separator defined in the ISA Envelope was getting replaced by a whitespace in the output file generated after the execution of the EDI X12 Outbound Transaction.

  • The output file generated after the execution of the EDIFACT Outbound Transaction did not contain the UNA segment.

  • In an EDI Outbound Transaction, when the Acknowledgement Requested field in the UNB Envelope was set to 0, the ACK reconciliation did not work even though the Expect Acknowledgement field was set to Yes.

  • The application did not support the special character - (hyphen) for the receiver Id and sender Id defined while creating the ISA Envelope, UNB Envelope, and Partner.

  • If the Repetition Separator in the UNB Envelope was left blank, the Release separator was placed between the two words separated by a space in the EDIFACT Output file.

  • You can now generate an UNA Segment in the EDIFACT Output file based on your requirement. To achieve this you need to select the Generate UNA Segment field.

    Warning Selecting this field is optional in case you go with Default separator values. However, you would need to mandatorily select the checkbox if you have changed any of the default separator value.

  • In the UNB Envelop, if Generate UNA Segment was selected, UNA05 was set as blank, and Segment Line Break was set to none, the EDI Outbound Transaction was getting aborted.

  • If the Repetition Separator (UNA 05) in the UNB Envelope had a space, the Release Indicator was placed between the two words separated by a space in the EDIFACT Output file.

Application package location​

Adeptia Connect application (AC v4.3) 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.