Skip to main content
Version: Adeptia Suite

6.9.18 Release Highlights

New features and improvements​

  • Support for processing multiple values in REST Consumer response headers 

    You can now process all the values, including the multiple entries under the same header key in a response header.  For more details, refer to this page. 

  • Access to Context Info and repository details for Non-EDI Relationships 
    You can now access the Context Info and the repository file details for a Non-EDI Relationship from the corresponding audit logs in Monitor > History.

  • Improved performance of Queue Processor 
    The Queue Processor (QP) has been optimized to ensure its threads remain consistently available for message execution, preventing the QP from getting stuck.

Security enhancements​

  • The following vulnerabilities in the application have been fixed:
    • IDOR - Insecure Direct object reference
    • Missing Content-Security-Policy header 
    • Unauthenticated access to repository and ImportPartner.csv files 
  • The following vulnerable jars have been removed: 
    • ini4j-0.5.4.jar
    • freechart-1.0.19.jar 

Bug fixes​

The following bugs have been fixed with this release:

  • When a user manually deleted the HTTP Event associated with Amazon S3—used as the source in a Process Flow—directly from the database, the application generated excessive event logs, which led to system instability. 

  • A Process Flow failed to execute when handling a large Excel file.
    A new property, abpm.schema.excel.poi.maxByteArray.size, has been added to configure the maximum number of bytes that can be processed from the Excel file at a time. 

  • Empty files were processed even when the Process Flow used a File Event with the Process Empty File option unchecked. 

  • The endpoint /rest/aisresources/edidatadictionary.jsp was accessible without user authentication.

  • The Non-EDI Routing files were not moved to the archive folder when the log cleanup and archival process was run. 

  • In a Process Flow with a Repeater Service generating many output streams, users were unable to scroll beyond the 12th stream or modify streams after that point. 

  • A Process Flow converting a large CSV file to JSON failed to execute and resulted in an error. 

  • A Process Flow with Excel as both the source and target Schema failed to execute because the output file exceeded the maximum number of allowed cell styles for date-formatted values.

  • While upgrading to v6.9.16, the migration process got stuck at the Select the object to promote objects step. 

  • When an Excel Schema was used as the source in a Process Flow, any large numeric values from the source file were represented in scientific notation in the output file. 

  • Users encountered an error when they attempted to edit an Excel Schema created using a definition file containing special characters in their sheet names and had the Process All Sheets option checked. 

  • When Excel Schema was used as both source and target in a Process Flow, the cell values that had comma and decimal places from the source file were represented as raw values causing inconsistent data format in the output file.
    To fix this a new property, abpm.schema.excel.enableNumericFormatting, has been introduced. Set this to true to fetch numeric values with commas and decimals from the source as display values in the source Excel file and format them with two decimal places in the Excel output. By default, this property is set to false. 

  • The Rest Provider could not parse large sized files and failed to execute.

  • When a mapping contained a Text Schema at the target with cloned nodes, the output could not be displayed in Grid view in the Data Viewer. 

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

  • Users were unable to connect to Azure Event Hub using a connection string containing a special character. 

  • When an array field in the source JSON Schema remained unmapped, the output file contained an empty string instead of an empty array. 

  • A string containing numeric values in the Source Schema was incorrectly represented as an integer in the output file when JSON Schema was used as the Target.
    To achieve this, apply the following mapping rule on the element that you want to be represented as a string:
    concat('${string:', <xpath of the source element>, '}')
    For example, concat('${string:', $Input_Emp_Record/Root/Record/city, '}') 

  • The Process Flow that used a Text Schema took longer than expected to process large text files. ​

  • Data Viewer in Mapping was taking longer than expected to load a source file that had a large number of records. 

  • The Mapping associated with Excel Schema failed when a field in the Schema contained special characters and whitespaces. 

    Warning
    • The application removes special characters from the fields' names. If removing the special character causes duplicate fields names, it appends an underscore (_) followed by a number in incremental fashion (for example, Field_1, Field_2) to the fields' names. In such a case, the original name of the field is neither visible in the Schema nor in the Mapping.
    • After applying this patch, you need to edit and save the Excel Schemas -- whose fields contain special characters or whitespaces -- created on the AC version v3.7.2 or above (up to v3.7.2.02.06)

  • Users encountered the error, “Unable to fetch entity from database”, when they logged in to the application with a Premier or Professional license. 

  • The Data Mapper failed to generate output for the input XML file when the file had large number of characters. This has been fixed by adding the property abpm.services.webmapper.debugger.setMaxCharacterLength which defines the maximum character length for the input XML file that the Data Mapper can parse for debugging the file. The default value for this property is 10000000.  

  • The mismatch between the Excel Schema field name and the corresponding field name in the Value Map caused the failure of the mapping associated with the Schema. 

  • When a mapping had a large number of nested level records, the generated XSLT displayed "undefined" for some of the elements. 

  • The target file contained record count, even when a source file without a header was processed in a Text Schema with Dynamic Header Support enabled. 

  • The Project XSL Templates could not be exported when both the Local and Project level XSL Templates were applied to the destination fields of a mapping. 

  • An Excel Schema failed to load in a mapping and users encountered an error when the Schema contained a pound sign in a field name.

    WarningIn case of an existing Excel Schema, you need to open it in edit mode and then save it to make it work.

  • After upgrading to v6.9.17, data failed to load in the Data Viewer section when an alert indicating a schema error was displayed.