...
Enhancements in logs archival and cleanup
Logs archival and 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/Template
You can now set the Logging Level, Repository File Retention, and Activities Logging Retention for a Transaction/Template 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.
...
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.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19287 |
|---|
|
- 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-19226 |
|---|
|
- - Already in release notes – Doc Jira is| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19762 |
|---|
|
- 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:
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.| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19365 |
|---|
|
- 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-19348 |
|---|
|
- While creating a Transaction, it was taking longer than expected to load the Partners on "Choose partner" screen.https://adeptia.atlassian.net/browse/ACE-19344%20-%20v3.5.28 - Doc Jira is
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19760 |
|---|
|
- 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.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.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19231 |
|---|
|
- 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-19280 |
|---|
|
- 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-19346 |
|---|
|
- 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. 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.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19690 |
|---|
|
- EDI Layout was not able to parse some of the SE segments causing blank SE segments generation in EDI file.
The EDI Layout (HIPAA_005010X223A2_837) failed to parse the SE segments in the source file.| 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 Excel Layout.| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19330 |
|---|
|
- Incorrect error message was being displayed when a field in the Source file could not be found in the defined Text Layout.
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.
...
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19267 |
|---|
|
- 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-19268 |
|---|
|
- 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. 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.
...
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.
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 97911fad-2290-35e3-b1ab-ad639316f8bd |
|---|
| key | ACE-19275 |
|---|
|
- 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-19272 |
|---|
|
- MESSAGE section on the application’s home screen did not show a welcome message to Partners when they logged in to the application.
