Versions Compared

Old Version 2

changes.mady.by.user Saurabh Gupta

Saved on

compared with

New Version Current

changes.mady.by.user Nitin Beri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Patch Name: AdeptiaSuite AdeptiaSuite_6_67_18April25July_2017.zip

Build Tag: Release_6_67_18April25July_2017

 

Info
titleApplies to

This This is the cumulative patch and can only be applied on Adeptia Suite v6.5 and later releases.If you want to 6 release with any of the following Build Tags:

    • Release_6_7_12June_2017
    • Release_6_6_18April_2017
    • Release_6_6_00_01_27April_2017
    • Release_6_6_00_01_04May_2017
    • Release_6_6_00_01_06June_2017
    • Version_6_7_22May_2017

To install Adeptia Suite v6.6 7 on a new environment, you need to download the  the installer from our website. Click Click here for  for the detailed instructions on installing Adeptia Suite.

If you want to To upgrade existing version of Adeptia Suite to v6.7, you need to apply the patch for the new changes. Click Click here for  for detailed instructions on applying the patch.

What’s new in this release?

  1. Support to Rerun the Aborted Process Flows
    A new option Rerun, is available in B2B logs to rerun aborted process flows, X12, and EDIFACT logs.

  2. Support for Choosing Ownership of the Migrated Objects
    While migrating the objects to a different environment, you can now define the ownership of the objects to one of the listed IT users at the target environment.

  3. Support for Processing Duplicate Files in an FTP or File Event
    You can now choose whether to process the duplicate files or not while creating File Event and FTP Event.

  4. Support for Default EDI Standard Version in Data Dictionary
    Now 05010 EDI Standard Version is also available as default in the Data Dictionary.

  5. Support to Allow Ignore Case Header fields in Text Schema
    A new option Allow Ignore Case, is available in a Text Schema to ignore the casing mismatches in the header of the schema and the data file.

  6. Support for Retain Activity in Migration Utility
    You can now retain objects at the target environment using Migration utility.Upgrade Saxon Version
    Data Mapper now uses Saxon v9.7 to map the elements. 

 

While mapping an empty value to the JSON target element, the value for that element in the generated target is displayed as { }.

Bug Fixes

Following are the issues that are fixed in this release.

  • If the Database Target is used as a target activity and mapping output contains an empty record (<Record/>) then database target activity processes records up to that empty record only. (Ticket #8029)
  • The patch application fails when Adeptia Suite is running on HSQLDB log database with size more than 350 MB.
  • Migration Utility does not run while using Salesforce or NetSuite as a solution with Solution.xml file in License.jar. (Ticket #8240)
  • An error message - "Address already in use" appears while restarting WebRunner when you stop Adeptia services in Linux.
  • All elements/attributes are not loaded while loading XML schema created by the DTD file with/without convert XSD in the Data Mapper.
  • All elements are not loaded in the Data Mapper while applying v6.5Mnt2. (Ticket #8438)
  • Changes are not reflected after changing the value of the user type in ldapconfiguration.properties file. (Ticket #8382)
  • Unable to make an LDAP group or a user of an LDAP group as a group admin. (Ticket #8392)
  • In case of an error, while testing any Text schema, the displayed error is not user-friendly.
  • On Oracle database, if the table AU_BUILDINFO exists in another schema that is not used in the Adeptia Server then patch deployment fails and displays the following error: Error while reading build tag from database. java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist. (Ticket #8375)
  • License Violation error is displayed on AIS home page even in case of correct license and without exceeding the limits. (Ticket #8383)
  • While using JSON Schema at target and map empty value with any element in mapper then in the target file, {} are generated for the empty value. 
  • The EDI outbound process flow gets aborted for some files while executing an EDI Outbound flow after upgrading the environment to Adeptia Suite v6.5. (Ticket #8466)
  • In the selected Data Mapper, selected schemas are not displayed while creating a Data Interface and mapping. (Ticket #8750)
  • RECEIVED status instead of an error is displayed while executing an Inbound relationship and mapping is aborted. (Ticket #8443)
  • The error is not displayed while executing an EDI file and the Skip Compliance check box is unchecked. (Ticket #8435)
  • Excel file skips the column with the blank header.  
  • When the separators of EDI schema are changed and saved then the values don't reflect in the EDI cache and EDI Schema output. (Ticket #8120)

    • In a clustered environment, if the admin password is changed then Error message HTTP 503 Service Unavailable is displayed on the System Console screen. (Ticket #8892)

    • In a clustered environment, when you upgrade Adeptia Suite to v6.5 System Console screen gets stuck while loading. (Ticket #7975)

    • When you are creating Text schema with \r\n as a record separator then an error is displayed - "Error found in uploaded: Upload correct file Error Message: Expected Record Separator = \r not found in data". (Ticket #8324)

    • When you deploy Web Service Provider objects twice at the target environment in non-interactive mode then the value of ‘Configure Process flow’ field is displayed as blank. (Ticket #8637)

    • Sometimes license activation failed due to an error in getting a number of CPUs. (Ticket #8588)

    • When you apply 6.6 patch then you would not be able to export Project objects. (Ticket #8800)

    • When you migrate a user from one environment to another environment and a user with the same name exists in the target environment then in the target environment two users exist with the same name and unable to login to Adeptia Suite. (Ticket #8070)

    • When you upgrade Adeptia Suite to v6.5 Mnt2 then multiple mappings are lost while opening the applet.

    • File Event doesn't send notification mail to the user if the base location provided in the event is not accessible.

    • If the JSON input file contains a long integer then in the output file it displays in the decimal format.

    • If an Excel source file contains a column with an empty header then data of this column is skipped and assigned to the next column.

    • When you validate XML schema, if any errors occurred in the XML file, then only one error is displayed.

    • If the XML contains a large number of namespaces then an error is displayed at the run time while creating data mapping activity.

    • It takes a long time to process HIPPA inbound file with a large number of Business Unit segments (for example, REF for 834) in the transaction set.

    • Fixed following data mapping related issues:

      • Speed of opening schemas/WSDLs

      • Mapping using full CPU utilization

      • Namespace prefixes are generated differently, breaking existing mappings

      • Source and Target schema does not load completely

      • Mappings complain about missing elements

      • Mapping cannot be opened: Error: NULL and Unable to retrieve schema from database

      • Namespaces not parsed unless schema is manually expanded completely

      • Data Mapper gets confused when loading source and target separately

    See also:

    Patch Deployment Guide