Versions Compared

Old Version 25

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 the important notes on this page this page.

  2. With an upgrade to JRE 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.

  • Changes in SAML implementation
    With an upgrade to JRE v17, the SAML implementation in Adeptia Connect has now got configuration changes. 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 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:

...

  • Users were able to access some of the REST APIs even when they did not use any authorization in the request.

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

  • Users were getting 404 error when they used a REST Consumer to hit a Snowflake's REST API via a proxy.

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.

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

...

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

...

  • The users were not able to expand some sub-loops when they loaded the EDI Layout on Source and Target mapping.

  • When the users uploaded a source file larger than 1 MB in the Mapper to test the mapping, the screen was getting stuck without throwing any error. To fix this issue an error message is now displayed when the user uploads a file larger than 1 MB in size.

Dashboard

  • The Dashboard did not show the User Id of the user who executed the Process Flow.

...

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