6.4 - 18 May 2016

Patch Name: AdeptiaSuite_6_4_18May_2016.zip
Build Tag: Release_6_4_17May_2016

 

Applies to

This is the cumulative patch and can only be applied on Adeptia Suite Version 6.3 Release with any of the following Build Tags:

  • Release_6_3_11Feb_2016
  • Release_6_3_01_26April_2016
  • Release_6_3_01_29March_2016

What’s new in this release?

 

  1. Supports Java 8

    Adeptia Suite now supports Java 8.
     

  2. System Console to Monitor Application Health & Usage

    You can now monitor the system and application resource utilization with the help of System Console. This replaces existing System Dashboard screen. The system console displays the information about licensing status, CPU usage, Kernal Information, WebRunner Information, and much more. This feature also allows you to set threshold value for alert information.
     

  3. Improvement in License Activation Mechanism 

    The new and improved License activation mechanism mandates all licenses to be activated for genuine identification. There are two ways to activate the license: Automatic and Manual. 
      

  4. Frevvo Upgrade

    Frevvo, which is an underlying component to create Rich Form, is upgraded from version 5.3.5 to version 5.3.9.
     

  5. Support to Define Multiple Partner Identifier

    You can now define multiple identifier for single partner in B2B outbound processing by using multi partner identifier.
     

  6. Support to allow single event to process multiple IDOC types files

    You can now process multiple types of IDOC file using one event rather creating events for each IDOC file type.

     

Bug Fixes

  • When you restart Adeptia Suite, installed on Linux machine, “License activation failed” error is displayed. (Ticket #7253, 7266
  • When YYYYMMDD date format is used in Current-Date or Date Format function of data mapper then the generated date is not correct. (Ticket #7324)
  • When Adeptia Suite is started in clustering mode using Windows Service, the Adeptia is unable to connect backend and log database. (Ticket #7370)
  • When you apply version 6.3 patch, in an environment where some of the accelerators are not deployed, then patch application rolled back. (Ticket #7433 7329
  • Incorrect error message is displayed when there is mismatch between Excel Schema definition and file being processed through it. (Ticket #7368, 7391)
  • When you open Event manage page and click View PF link then error is displayed. (Ticket #7292)
  • When you load the EDI 837 file having multiple HI Segments and HI0101 composite element is present in that segments then the structure of EDI Schema Output is not correct. (Ticket #7237)
  • In EDIFACT Outbound, escape character/release character functionality is not working when Segment Line Break is defined as Carriage return, Line feed or both. (Ticket #7363)
  • When you apply patch on Adeptia Suite, which is using Oracle database as backend and log the pre-requisites check fails with “Insufficient database permission” error. (Ticket #7322)
  • IDOC number link in SAP log page doesn’t work.
  • In case there is an error while sending or receiving an IDOC, the column "Error" in SAP Logs doesn’t display any error details.
  • While creating IDOC schema in online mode, IDOC extensions are not displayed in the IDOC type dropdown list.
  • In B2B outbound processing, in case source file is XML of XML ver. 1.1, the process flow execution aborts.
  • When you load XML Schema (created by xsd file without namespace) in data mapper with On Demand Optimized loading then elements are not loaded in Mapper.