New features and improvements
...
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.
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.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.
While creating a Transaction, it was taking longer than expected to load the Partners on "Choose partner" screen.
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.
Users encountered an error while trying to update the Routing Type for an existing EDI Outbound Transaction having Content Based routing.
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.
...