Skip to main content
Version: 4

AC v4.5 release highlights

New features and improvements ​

  • Improved efficiency with child Process Flow distribution among runtime pods 

    • Adeptia Connect now comes pre-bundled with Redis, allowing child Process Flows to execute asynchronously across multiple runtime pods, enhancing efficiency and scalability for high-volume processing.​​​

    • You can now configure the concurrency level for child Process Flows on shared (via values.yaml) or dedicated runtime pods (via UI) to optimize performance and resource utilization. Click here for more information.

  • New OAS 3.0 document based app connector

    Adeptia Connect now integrates the Microsoft Dynamics CRM connector that uses a document (OAS 3.0) based framework. To learn more, refer to the Microsoft Dynamics CRM section. 

  • Enhanced Azure Blob connectivity with multiple Client IDs and Secrets

    Adeptia Connect now supports connecting to Azure Blob via Azure AD, using multiple Client IDs and Client Secrets within the same Tenant ID. To learn more, refer to the Azure Blob section. 

  • 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. Click here for more information.​

  • **Performance improvement in Advanced Database Source
    **

    While defining an Advanced Database Source, 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.

  • Improved performance in JSON Layout at Target
    While defining a JSON Layout at the 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. Click here for more information.

Security enhancements 

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

Bug Fixes

  • The users were unable to retain the project config mapping activity when they migrated objects from one environment to another. You can now view the mapping id of the Project-Git Mapping activities by clicking Account > My Company > Project-Git Mapping > More > View.

  • Users were unable to retrieve the access token, required for accessing an API endpoint, via an OAuth account that was configured with an OAuth Profile.

    This has been fixed by adding the option to include a security policy while creating an OAuth Profile. The security policy you use defines the SSL configuration, including the required certificates and/or keys. Refer to this page to learn more.

  • You can now dynamically set the value for Blob Tags in Azure Blob by following the steps given below:

    1. Go to the required Process Flow.

    2. Double-click the Azure Blob Application Target whose Blob Tags you want to set dynamically. This opens the Activity Properties panel of the Application Target.

    3. On the Activity Properties panel, select the VARIABLES tab.

    4. In the Type field, select Activity.

    5. In the Name field, select parametersJson. 

    6. In the Value field, set the dynamic value for Blob Tags in the following JSON format:

      {"BlobTags":"Var1=value1,Var2=Value2"}

      Where, Var1=Value1 is the first dynamic value (in key-value pair) and Var2=Value2

      is the second dynamic value for the Blob Tag. You can add more values separating

      them by commas.

    7. Click Save.

  • The Process Flow failed to execute when Optimize Processing was enabled for the Advanced Database Target, and the database table name in the associated Advanced Database Layout included special characters. 

  • The Process Flow using a REST Consumer with an associated Security Policy failed to execute when the OAuth access token expired.

  • When a source file with multiple sheets, some containing blank field values, was used in an Excel Layout, the resulting output file did not include a header.

  • When an Excel Layout with duplicate field names was used at the target end, the output file appended a numeric suffix to the repeated field names.

  • The application failed to authenticate to the ASB Listener namespace when there were multiple namespaces configured with Shared Access Signature authentication on the Azure portal.

  • A Process Flow triggered via the ASB Listener ran on the shared runtime pod, even when configured to run on a dedicated runtime pod.

  • Users were unable to create an Advanced Database Layout using Kerberos With Service Account authentication type for an Oracle Database.

  • The Process Flow failed to execute when the Advanced Database Source being used contained field names starting with a numeric value.

  • API calls using an access token were failing with an "HTTP 401 Unauthorized" error.

  • The users were not able to download and view a large-size XML file from the repository view.

  • When a parent Process Flow was triggered by an event, its child Process Flows were not nested under it and appeared separately on the Dashboard’s Transactions tab.

  • The long numeric values in a JSON data file were converted to exponential values when processed through a JSON Layout. 

Known issue

  • When child Process Flow distribution is enabled, EDI Transactions do not complete as expected and instead remain stuck in a running state.