Versions Compared

Old Version 28

changes.mady.by.user Ashhad Alam

Saved on

compared with

New Version Current

changes.mady.by.user Shruti Pasayat

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

New features and improvements

...

Tip

Important

  1. As this is a major upgrade, it is recommended that you apply this patch to a test environment before applying it to production. To know the impacts, refer to this page.

  2. With an upgrade to the important notes on this pageJRE v17, the SAML implementation in Adeptia Connect has now got configuration changes. To learn more about SAML in Adeptia Connect, refer to this document.

  3. 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.

...

    • .

...

  • 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 Security Policies using APIs provided by Adeptia Connect. 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).

  • Bulk activation and deactivation of Transactions, Events, and Templates
    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 folder name for EDI file in Transaction at runtime
    While creating an EDI Transaction you can use a context variable, $$PARTNER_NAME$$, to create the archive folder for EDI file at runtime based on the Partner name. 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 Connector apps for a Transaction/Template are as follows:

...

  • 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.

...

  • 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.

  • MESSAGE section on the application’s home screen did not show a welcome message to Partners when they logged in to the application.

  • The users were facing GUI issues while editing a Non-EDI Outbound Relationship that had more than 4000 FTP Target types to select from.