New features 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 |
---|
Important
|
Enhanced SAML implementation
With an upgrade to JRE v17, the SAML implementation in Adeptia Connect has also now got enhancements. To learn more about SAML in Adeptia Connect, refer to this document.Token-based authentication for NetSuite
You now need to use token-based authentication to connect to a NetSuite account. Click here for more information.Support for creating Security Policies using an API
You can now create the following types of Security Policies using APIs provided by Adeptia Connect.WS Consumer
WS Provider
HTTP Source
For more information, refer to this page.
Exporting objects without the repository folder in offline migration.
While performing offline migration, you can now choose to skip exporting the Process Flow repository files. For more details, refer to the documents on Export and Backup using Windows and Linux.Detailed information via Email notification in case of EDI Transaction failure.
The translation error details will now be sent as an attachment with the email notification in case of a failed EDI Transaction ( for X12, EDIFACT, and HIPAA EDI standards).Activation and Deactivation of multiple activities
You can now choose to turn ON/OFF multiple Transactions, Events, and Templates from the list displayed on the current manage page for each of these activities. For more details, refer to this page.Context Variable for defining the Archive archive folder name for EDI Transactions at runtime
While creating an EDI Transaction you can use a context variable, $$PARTNER_NAME$$ to create the Archive archive folder at runtime based on the Partners namePartner who runs the Transaction. Click here for more details.Additional cron expression to define firing schedule for Events, Transactions, and Templates
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. For more details, refer tothis page.
The list of supported Events and Applications Connector apps for a Transaction/Template are as follows:
Supported Events |
| ||
---|---|---|---|
Supported ApplicationsConnector apps |
|
|
|
...
Enhancements in Logs Archival logs archival and Cleanup cleanup
Logs Archival archival and Cleanup cleanup feature has now been improved to offer more reliability and better performance. For more details, refer to this section.Support for special characters in the header of an Excel layout
An Excel layout now also supports and parses data with special characters in the header of the layout.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.Override Advanced Settings for a Transaction
You can now override the Logging Level, Repository File Retention, and Activities Logging Retention settings for a Transaction at runtime in Adeptia Connect. For more details, refer tothis page.Enhancements in Advanced Text Layout
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.
...
- After AIS to AC migration, 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.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19148 The users were not able to change the property values for an existing Record Queue Producer migrated from AIS to AC.
- After migrating from AIS to AC, the users were not able to make and save any changes to an existing Process Flow's activity that had spaces in its alias name.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19302
- After migrating from AIS to AC, users encountered an error in all the Process Flows that had a WS Consumer activity.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19680
Transaction
In a Template/Transaction, when the users used Amazon S3 with its Bucket in the US East zone, the application threw an error while browsing the file on Select File Location step.
While creating a Transaction, it was taking longer than expected to load the Partners on "Choose partner" screen.
Users encountered an error while trying to update the Routing Type for an existing EDI Outbound Transaction having Content Based routing.
- After setting a value for the Mode Type field (on the File Generation Policy screen) in an EDI Transaction and moving to the next step, the application was resetting the field's value to Create when the users visited the Choose App screen (under Set Destination category) again without saving the Transaction.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19287
- - Already in release notes – Doc Jira isJira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19226
- Some segments in the EDI Acknowledgement File were not getting generated as per EDI Standards. This has been fixed by adding the property abpm.edi.removeSegmentSuffixAndLoopPrefix. You can set the value for this property to yes to remove the suffix from a segment's name and the prefix from a loop's name to be recorded in IK3 segment in 999 or 997 acknowledgement file. Follow the steps given below to configure this property:Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19762
1. Click Account > Settings.
2. Expand Server Nodes Settings in the left panel.
3. Select the server node.
4. Click Edit.
5. Go to Solution Properties > EDI Solution Parameters.
6. Set abpm.edi.removeSegmentSuffixAndLoopPrefix to yes.
7. Click Save.
8. Click Reload to bring the changes into effect. A confirmation message is displayed confirming that the configuration has been reloaded.
9. Restart the Connect Server.
- A Transaction that used Azure Blob as the Source picked up all the files for processing even when it was defined to process a specific file.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19365
- While creating a Transaction, it was taking longer than expected to load the Partners on "Choose partner" screen.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19348 https://adeptia.atlassian.net/browse/ACE-19344%20-%20v3.5.28 - Doc Jira is
- The Transactions that used BambooHR Connector as a Source failed to execute when the user (API key used in the Connector) had permissions to access the details of some employees but not the others. This has been fixed by adding the property bamboohr.failOnNoAccessPermission with false (default) as its value to the adapters.properties file located at …/<Adeptia Connect Install Folder>/ConnectServer/AdeptiaServer/ServerKernel/etc.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19760 When the property is set to false, the details regarding the inaccessible data are logged in the Dashboard > Trigger > Logs with relevant error message.
Setting this property to true prevents the user to process the details of any employee if the user doesn’t have access to even a single employee in BambooHR.
- Users encountered an error while trying to update the Routing Type for an existing EDI Outbound Transaction having Content Based routing.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19231
- v3.7.1.6 - When the user edited an EDI Outbound Transaction, the option selected in the ISA Envelope field (on the EDI Configuration screen) was getting unselected and required a re-selection.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19280
Layout
- 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.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19346 The users were not able to move to the next screen when they selected an EDI specification and clicked OK on the Select EDI Specification screen while creating an EDI Layout.
- EDI Layout was not able to parse some of the SE segments causing blank SE segments generation in EDI file.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19690
The EDI Layout (HIPAA_005010X223A2_837) failed to parse the SE segments in the source file.
- Incorrect error message was being displayed when a field in the Source file could not be found in the defined Excel Layout.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19331
- Incorrect error message was being displayed when a field in the Source file could not be found in the defined Text Layout.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19330
Data Dictionary
Users were not able to save changes to the records while creating or editing a Positional Data Dictionary.
While creating an Advanced Positional Layout, when the users used Data Dictionary, they were not able to make and save changes to the records.
...
- Users were able to access some of the REST APIs even when they did not use any authorization in the request.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19022
- When the users hit a specific REST API, they were able to see sensitive data even when they were not logged in to Adeptia Connect application.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19343
Logs
- The PDF generated in the EDI interchange logs pages for an EDI Transaction was not in correct format when Advanced Positional Layout was used at the Target.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19267
- 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.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19268 In case of multiple EDI Inbound transactions using the same template, even when no transaction had the trading partner id same as that in the Source, the system showed logs for the first transaction.
...
- The users were getting an error message on the Web Process Designer when the stream generated from an activity was not being consumed.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19277 On changing the alias name of a CALL action in a Process Flow, the associated variables were not displayed in the Variable Name field of the variable's Activity Properties screen.
- When the users tried to edit a Process Flow from within the Project manage page, they were getting redirected to Edit Template screen.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-18930
- When a SOAP Consumer used in a Process Flow encountered an error, no activity next to it could be executed.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19349
- 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.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19128
- 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.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19035
Event
- Doc jira isJira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19317
- The process flow bound with an FTP Event logged a message in event log every time it encountered a file of 0Kb size and failed to execute that file. This bug has been fixed by introducing the option Process Empty File in the FTP Event to enable processing of even an empty file.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19761
Mapping
- The users were not able to expand some sub-loops when they loaded the EDI Layout on Source and Target mapping.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19316
Dashboard
- The Dashboard did not show the User Id of the user who executed the Process Flow.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19350
Stored Procedure
- v3.5.1 - The system threw an error when the user tried to save a Stored Procedure having In Params (input parameters) value of more than 256 characters.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19281
Users
- The verbiage of the Partner user invite was not correctly articulated.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19257
Services
AIMap service failed to start on Linux-based systems.
...
Some UI elements were not working properly after the recent browser updates.
Users were not able to open the applets because of the expired certificate.
- FAVORITE TRANSACTIONS section on the application’s home screen showed broken icons for all the Custom Connectors.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19275
- MESSAGE section on the application’s home screen did not show a welcome message to Partners when they logged in to the application.Jira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19272
Other new bugs
- TBD with Bhavuk BalujaJira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-17036
- TBD with Satyam SharmaJira Legacy server System JIRA serverId 97911fad-2290-35e3-b1ab-ad639316f8bd key ACE-19377