Skip to main content
Version: Adeptia Suite

6.9.16 Release Highlights

New features and improvements​

  • File Download option in Advanced Positional Schema
    While editing an existing Schema, you can now download the XSD, hierarchy XML, and the field file for the Advanced Positional Schema based on your requirement. For more details, refer to  this page. 

  • Performance improvement in Advanced Database Target 

    While defining an Advanced Database Target, you now have the option to optimize the performance for processing of high volume of records by tuning the number of records that can be processed simultaneously. Click here to learn more. 

Security enhancements​

  • The third-party jar mentioned in the table below has been upgraded to remove critical and high vulnerabilities in it.

    Old version 
    		Updated version 
    snakeyaml-1.33.jar
    		snakeyaml-2.0.jar

  • The version of jQuery in Adeptia Suite has now been upgraded from v3.5.0 to v3.7.0 to remove critical and high vulnerabilities in it. 

  • The application now doesn't allow you to download a file that lies outside anywhere of the ServerKernel folder.

  • The application now doesn't allow you to download a file other than wsdl.

  • Some of the expired certificates have been updated.

  • The following security issues have been fixed :

    o HttpOnly Keyword Not Set In Cookies

    o Insufficient Cache Control

    o Account Password Hashes Disclosed 

Bug fixes​

The following bugs have been fixed with this release:

Schema​

  • While creating a PDF Schema, the misaligned contents in the file are not rendered correctly in the Schema.

  • Users were not able to remove a child node from the hierarchy while editing an Advanced Text Schema.

Web Services​

  • On deleting a SOAP Consumer the corresponding WSDL File Reference also got deleted.

Logs​

  • The application logs (Kernal and webrunner logs) cleanup was not working for the secondary node in case of a clustered environment of Adeptia Suite.

Process Flow​

  • When a Process Flow ended abruptly, it showed the incorrect Repository path.

  • A Process Flow with Repeater Service was not able to add multiple input streams. 

  • The Process Flows were getting aborted when the users enabled JTA Enlist in Advanced Database Target.

Mapping​

  • When an user attached the source file in the Data Mapper and previewed the output record, the mapping was getting saved even when autosave was disabled.

  • The DB query function used in a mapping threw an error when Connection Pool was enabled in Database Info.

  • Users were unable to copy a mapping and the associated local variables from one data mapper to another using the Copy Mapping option.

  • A mapping was getting saved when the users attached a file and generated the output in Data Viewer, even when the autosave for the mapping was disabled.

  • The Mapping manage page took longer than expected to load.

  • The Mapping manage page displayed incorrect order of mapping names when sorted alphabetically.  

Users ​

  • SAML users once logged into the application were unable to logout.

Services​

  • An FTP activity was not able to establish connection with the SFTP server using the new algorithm.

  • Users were unable to stop Adeptia Suite Kernel service in Windows.

  • The execution of an Advanced Database Target failed when the associated Database info with JTDS SQL driver had Hikari as the Connection pool.

Log cleanup and archival​

  • Users were not getting mail notification in case ArchivalandCleanup fails.

  • After executing the ArchivalandLogCleanup, the logs were not getting retailed as per the specified retain time.

  • The application sometimes threw the error "Archival is not enabled" during the log cleanup and archival process.