New features and improvements
Upgraded Amazon Corretto JRE to version 17
The bundled Amazon Corretto JRE has now been upgraded from Java version 8 to version 17 ensuring regular security updates.Tip title Important With this upgrade, the JMS provider that connects to Apache Active MQ JMS server now uses the two jars activemq-core-5.7.0.jar, and geronimo-j2ee-management_1.1_spec-1.0.1.jar. Ensure that:
- You use these two jars when you create a JMS provider that connects to Apache Active MQ JMS server.
- You have updated any existing JMS provider that connects to Apache Active MQ JMS server to use these two jars.
For more details, refer to this page.
- Upgraded Spring Boot framework to version 3.0
The Spring Boot framework has now been upgraded to version 3.0 for better performance and stability. - Enhanced SAML implementation
With an upgrade to Sprint Boot version 3, the SAML implementation in Adeptia Connect has also now got enhancements. - Support for Solution Promotion from web UI
Adeptia Connect now brings an improved user interface to let you carry out Solution Promotion (export and import). Click here for more information. - Enhanced Runtime autoscaling using KEDA
Apart from CPU and Memory, autoscaling of Runtime pods can now also be achieved based on the number of messages in queued state. Click here for more information. Limit the asynchronous request processing based on resource availability
Apart from the synchronous requests, you can now also limit the asynchronous requests processing on a Runtime pod based on resource availability (CPU, or memory, or both). To achieve this, you can use the following two configurable threshold properties. Click here for more information.- readiness.probe.cpu.threshold
- readiness.probe.memory.threshold
- Support for external JWT token authentication in REST Provider
Adeptia Connect now allows you to use a token issued by a third party to access a published REST API. Click here for more information. - Support for defining a REST provider by using Swagger YAML/JSON
You can now import an OAS 3.0 standards based Swagger YAML/JSON file to define a REST Provider. Click here for more information. - Password ageing policy
You now have the option to configure the expiry time for the user login password. Click here for more information. - Support for Azure Files connector
Adeptia Connect now lets you use Azure Files as a Source or Target in a Template/Transaction. Click here for more information. - Support for Layouts to read files having data in array format
The following Layouts can now parse the files having data in single or composite array format. Click here for more information.- Text
- Positional
- Advanced positional
- Advanced text
- Improved AIMAP stability and performance
Following improvements have been made in the AIMAP feature to make it more stable.- Schema embedding information that helps in giving the mapping suggestions is now saved in the database instead of files to maintain the data security and integrity and enhance the performance.
- Adeptia Connect now introduces an environment variable AIMAP_BACKEND_URL to define a DB URL (in Python compatible format) for AIMAP to connect to the Backend Database. Click here for more information.
- Reduced startup time for microservices pods
Microservices pods startup time has now been reduced. - Support for Kerberos authentication for Oracle database
You can now configure Kerberos authentication for Oracle database (Backend, Log, Quartz, and Log archive) by setting the relevant environment variables in the values.yaml file. For more details, click here. - Support for Kerberos authentication for Oracle database in DB Info
You can now configure Kerberos authentication for Oracle database while creating a Database Info. For more details, click here. - Remove mapping or apply filter on multiple fields in one go
You can now remove mapping or apply filter on multiple fields in one go without having to perform these tasks for each field individually. Click here for more information. - Support for messages aggregator and splitter in JMS connector
You can now aggregate and split messages in JMS Event and Target activities respectively. For more details, refer to the pages JMS Event, and JMS Target. - Extract field names from a Layout
You can now extract the names of the fields in a Layout using an API Endpoint. Click here for more information. - Enhancements in Logs Archival and Cleanup
Logs Archival and Cleanup feature has now been improved to offer more reliability and better performance. - Token-based authentication for NetSuite
You now need to use token-based authentication to connect to a NetSuite account. Click here for more information. - Updated actions for BigCommerce
A set of new actions for BigCommerce has been added. - Introduction of Admin Restricted role
You can now log in to the application as a less privileged Admin Restricted (newly added user role) with access limited to the followings:- Dashboard
- My Profile
- My Company
- Settings
- System Console
- Maintenance
For more details, refer to this document.
- Updated actions for Azure Blob target
Some actions have been updated for Azure Blob target. For more details, refer to the documents Azure Blob Target and Azure Blob. - Configurable wait time for a blob to become stable
You can now provide a wait time for the file to become stable before the Azure Blob Event gets triggered. For more details, refer to this page. - Display files size fetched by Azure Blob Event and Source
The Dashboard now displays the size of the files fetched by an Azure Blob Event and Source. For more information, click here. - Support for Admin user to import the User type of objects
The application now also enables any Admin user to import the User type of objects from one environment to the other. For more details, refer to this document. - Support for OAuth in Microsoft Dynamics CRM connector
You can now use OAuth as the authentication type in a Microsoft Dynamics CRM connector. Click here for more information. - 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. Click here for more information. - Kafka Listener failure email notification
While creating or editing a Kafka Listener, you can now provide the email ids of the users to whom you want to send email notifications in case of its failure. Click here for more information. - Open a repository file in a new browser’s tab
You can now open a repository file in a new browser’s tab instead of downloading them from the logs available on the Adeptia Connect dashboard. - Run Now option for an inactive Transaction and Template
You can now use the Run Now option to execute a Transaction manually even if the Template/Transaction is not in active state. For more details, refer to this document. - 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. - Support for retaining the special characters in a JSON layout
You now have the option to retain the special characters, for example, \n,\r, in a JSON data file by configuring the property abpm.connect.jsonschema.retainSpecialCharacters. Click here for more information. 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 Data Encoding
You can now add and use a standard Data Encoding of your choice while creating a Template. Click here for more information. - 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. Option to create a copy of an EDI Template/Transaction
You can now create a copy of an existing EDI Template/Transaction and modify it as per your need. For more details, refer to the pages Copying an EDI Template, and Copying an EDI Transaction.- 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. - 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. - Support for Sys Admin to update his email id
As a Sys Admin you can update your email id from the My Profile screen. 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. - 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. Send one or more payloads to a REST Consumer
You can now send one or multiple payloads along with the file to a REST Consumer. Click here for more information.
...
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.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
...
- 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.
Variable
Default value
BACKEND_ABANDONED_CONNECTION_TIMEOUT 10
BACKEND_INACTIVE_CONNECTION_TIMEOUT 60
BACKEND_QUERY_TIMEOUT 60 BACKEND_FAST_CONNECTION_FAILOVER_ENABLED true LOG_ARCHIVE_ABANDONED_CONNECTION_TIMEOUT 10 LOG_ARCHIVE_INACTIVE_CONNECTION_TIMEOUT 60 LOG_ARCHIVE_QUERY_TIMEOUT 60 LOG_ARCHIVE_FAST_CONNECTION_FAILOVER_ENABLED true LOG_ABANDONED_CONNECTION_TIMEOUT 10 LOG_INACTIVE_CONNECTION_TIMEOUT 60 LOG_QUERY_TIMEOUT 60 LOG_FAST_CONNECTION_FAILOVER_ENABLED true QUARTZ_ABANDONED_CONNECTION_TIMEOUT 10 QUARTZ_INACTIVE_CONNECTION_TIMEOUT 60 QUARTZ_QUERY_TIMEOUT 60 QUARTZ_FAST_CONNECTION_FAILOVER_ENABLED true
Adeptia Connect v4.2.6.3
...
| Warning | ||
|---|---|---|
| ||
The upgrade to AC v4.2.6.3 is certified only on AC v4.2.6_Beta. |
New features
- The runAsNonRoot parameter has now been defined at container level.
- An individual bundled A non-root user has now been assigned to 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 added to all the deployments to send traces related to proxy to datadog.
- You can now configure Git proxy by following the steps given below.
- Open the deployment file of webrunner.
- Add -Djdk.http.auth.tunneling.disabledSchemes="" to the JAVA_OPTS variable.
- Log in to the Adeptia Connect.
- Click Account > Settings.
- Expand Miroservice Settings in the left panel.
- Select WebRunner.
- Expand Version Control.
Update the properties described in the following table.
Variable
Default value
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.
...
The following environment variables have been added to the global > environmentVariables section in values.yaml file.
Variable
Default value
BACKEND_ABANDONED_CONNECTION_TIMEOUT 10
BACKEND_INACTIVE_CONNECTION_TIMEOUT 60
BACKEND_QUERY_TIMEOUT 60 BACKEND_FAST_CONNECTION_FAILOVER_ENABLED true LOG_ARCHIVE_ABANDONED_CONNECTION_TIMEOUT 10 LOG_ARCHIVE_INACTIVE_CONNECTION_TIMEOUT 60 LOG_ARCHIVE_QUERY_TIMEOUT 60 LOG_ARCHIVE_FAST_CONNECTION_FAILOVER_ENABLED true LOG_ABANDONED_CONNECTION_TIMEOUT 10 LOG_INACTIVE_CONNECTION_TIMEOUT 60 LOG_QUERY_TIMEOUT 60 LOG_FAST_CONNECTION_FAILOVER_ENABLED true QUARTZ_ABANDONED_CONNECTION_TIMEOUT 10 QUARTZ_INACTIVE_CONNECTION_TIMEOUT 60 QUARTZ_QUERY_TIMEOUT 60 QUARTZ_FAST_CONNECTION_FAILOVER_ENABLED true - 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.
Application package location
...