Versions Compared

Old Version 1

changes.mady.by.user Nitin Beri

Saved on

compared with

New Version Current

changes.mady.by.user Saurabh Gupta

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_6_34_19Feb18May_2016.zip
Build Tag: Release_6_34_11Feb17May_2016

 

Info
titleApplies to

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

  • Release_6_23_SP211Feb_01Oct20152016
  • Release_6_23_SP201_0126April_27Oct20152016
  • Release_6_23_SP2_01_05Nov2015
  • Release_6_2_SP2_02_10Dec2015
  • Release_6_3_02Feb_29March_2016

What’s new in this release?

 

  • When you deploy the Patch, at the time of accelerator deployment duplicate entry warning messages are displayed.
    • When you deploy the Patch and accelerator also deployed then existing configuration of accelerator activities does not retained

    1. Applets supporting Java 8 

      Now all applets of Adeptia Suite (Process Designer, Process Modeler, Data Mapper, etc.) support Java 8.
       

    2. Support for Kerberos authentication 

      Supports Java 8

      Adeptia Suite now supports Kerberos authentication at the transport level. Java 8.
       

      Delete all queued process flows 

    3. System Console to Monitor Application Health & Usage

      You can now delete all queued process flow with one click from Adeptia Suite's maintenance GUI.
       

    4. Common shared path for all nodes of a cluster

      You can now configure common shared path to store all intermediate files and folder, and share with all the nodes of the cluster. While setting up the clustering, you have to configure only one shared path where all the intermediate files such as, value map, XSL templates, WSDLs, and repository etc. will be stored (Ticket #6099).
       

    5. Improved HIPAA parsing logic

      Adeptia suite now has an improved HIPAA parsing logic that is compliant with HIPAA standards and can catch any deviation.
       

    6. Improved patch deployment and recovery process

      With improved patch deployment & recovery process, your will have to now put minimum efforts for manual changes after the patch deployment.

       

      7. Improved License validation mechanism

      License validation mechanism is improved to support online and offline activation. It is mandatory to use new license after this upgrade. Now onward, all the licenses will be node-locked, that is, one license can be used on one machine only.  

    Bug Fixes

     

  • The Data Mapper's value maps become inaccessible after you upgrade to Java 1.8 on client machines. (Ticket #6731)
  • When you apply extension element on clone nodes, then extension element disappears if you open the mapping in edit mode. After applying this patch, to bring this fix into effect for existing activity you need to open the existing data mapper activity, change the extension of clone elements and save the activity. (Ticket #3122)
  • When any new line character is used in description of user and if this user opens any data mapper activity then applet doesn't open. (Ticket #6432)
  • During patch deployment a message is shown to backup all the rich forms, whereas it is not required. (Ticket #6759)
  • Unserialize vulnerability in commons collection API has been fixed. (Ticket #6748)
  • When any error occurs in Database event's update query then email notification is not sent. (Ticket #6932)
  • When there is an extra segment terminator at the end of the file in EDI X12 then EDI process flow fails while processing this file.
  • When you use Character Set Encoding other than ISO-8859-1 in server-configure.properties file or in REST Provider activity then the source zip file fetched from the REST provider gets corrupted.   (Ticket #6060). For detail refer https://support.adeptia.com/hc/en-us/articles/207776876
  • When you check the references of any process flow having child flow but child flow does not exists then an error is displayed. (Ticket #6720)
  • Adeptia Suite is Vulnerable to RC4 ciphers. Now, RC4 ciphers are added in jetty.xml file within excluded ciphers list.  (Ticket #6699)
  • When you create the Data interface activity with Open LDAP and browse the table then an error is displayed. (Ticket #6869)
  • When you create the custom webform with jsp file and open the form after publishing the form then an error is displayed. (Ticket #6978)
  • When a child Process flow executed in loop through call action then ‘OutOfMemoryError’ occurs in execution. (Ticket #6831)
  • When you create excel schema activity without Data Header Present then an error is displayed in Process flow execution and in Schema Test button output. (Ticket #7032)
  • When you create Advanced Database Schema you cannot edit the query manually in Query field without browse table. Now, Query field is editable. (Ticket #6805)
  • When you save as the data mapping activity and open it, remove the target schema and load same target schema again and import mapping and save the new created mapping activity then an error is displayed. (Ticket #5375)

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

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

    3. Frevvo Upgrade

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

    4. Support to Define Multiple Partner Identifier

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

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