Versions Compared

Old Version 34

changes.mady.by.user Nitin Beri

Saved on

compared with

New Version 35

changes.mady.by.user Nitin Beri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Patch Name: AdeptiaSuite_6_5_02_25Nov_2016.zip

Build Tag: Release_6_5_02_25Nov_2016

 

Info
titleApplies to

This patch can be applied on Adeptia Suite Version 6.5 Release.

To find the changes or updates easily in the documentation, the new features have been highlighted with the text in blue color in the respective pages.

What’s new in this release?

  1. Support for SAML SSO Authentication
    You can now configure Single Sign-on (SSO) in Adeptia Suite, using Security Assertion Markup Language (SAML).  Click here to know how to configure SSO using SAML. 

  2. Support of Response Header in REST Provider
    You can now create your own response header for REST Provider and can also override the response header at run time.

  3. Global Search
    With this new feature, you can now search for any service from anywhere in Adeptia Suite.

  4. JDBC Drivers for Apps in Data Interface
    Drivers for all the apps in Data Interface has been updated.

  5. View FA Statuses for Outbound in B2B logs
    New FA status added for Outbound reconcilation in B2B logs.
    New FA Status: ACCEPTED (A), ACCEPTED (E), PARTIALLY ACCEPTED (P), REJECTED (M), REJECTED (R), REJECTED (X), and REJECTED (W). 

  6. Support of Query String in API Key 
    You can now pass API key as a part of query string. 

  7. Add On Features in Professional Edition of Adeptia Suite
    Dynamic Process Flow and Web Service Consumer are now available as add on features in the Professional edition of Adeptia Suite.

  8. Time Stamp with %% in Target File Name for Inbound/Outbound Relationship
    You can now add time stamp with %% in the target file name for inbound/outbound relationship. Visit the following pages for more information:
    Creating Inbound Relationship for EDI data
    Creating Inbound Rlationship for Non-EDI data
    Creating Outbound Relatinship for EDI data
    Creating Outbound Relationship for Non-EDI data

  9. Support for Overriding Target File Name in Non-EDI Inbound/Outbound Relationship
    You can now override the target file name with/without time-stamp for the following target types: File Target, FTP target, and LAN File Target in Non-EDI inbound/outbound relationship.

  10. New Date-Format and Time Stamps in EDI Inbound/Outbound Relationship
    New date formats and time stamps are added in EDI inbound/outbound relationship.

  11. Improved Log Cleanup
    Data can now be deleted chunks, while running log cleanup, from MySQL database.

 

Bug Fixes

Following are the issues that are fixed in this release.

  • When you finish overdue task from Task Manager one by one then sometimes process flow get aborted and error is displayed in the Kernel logs. (Ticket #7621)
  • Unable to override the target file name with/without time-stamp for target types - File Target, FTP target, LAN File Target, in Non-EDI Inbound/Outbound relationship. (Ticket #7163)
  • When you remove schema from Data Mapper, schema intended to be removed stays intact. (Ticket #7477)
  • While importing objects using the Non-Interactive Migration Utility, you are unable to override project group during object/s deployment. (Ticket #7655)
  • When you search using any criteria in B2B logs then in the search result, same links are displayed in FileIn and FileOut column.
  • Mapper is not able to load the child of Advance database schema node,  when the node is already present in the node hierarchy.
  • In Mysql Database, when you execute EDI Inbound for reconcilation twice for an outbound message, then All and X12 Outbound displays an error.
  • When you view Data Interface logs, latest logs are displayed at the end.
  • When you configure pf repository path (abpm.repository.root) and if it doesn't contain word "repository" then PF repositories are archived to some other location.
  • When you try to update GS segment in the database, error is not handled in a proper way.
  • In some environments, sometimes outbound process flow gets aborted and throws XML DB exception.
  • On some browsers, while creating or editing Data Mapping activity from Data Interface, JNLP file fails to download.

  • On X12 Inbound and Outbound log page, when you search on the basis of FA Status, then relevant values of Inbound and Outbound FA Status column are not displayed.

  • If a secondary node goes out of network and resumes after sometime, it does not participate in cluster.
  • If Field name consists of space and Dynamic header support is checked then Error message (Header: <Header_name> not found in data) is displayed at run time.
  • When a partner identifier is configured for an IDoc extension like ZINVOIC then on drop of file, error is thrown for no relationship found.
  • Data Interface and KPI dashboard is dashboards are not displayed to other users of same group. 
  • When you create Adv. Positional schema with the given xsd and change the hierarchy of records in edit mode, then error records are generated and String Index out of bound exception is displayed in Error.xml file and webrunner logs.
  • You are able to delete the event even if it is bound with Data Interface. 

See also:

Patch Deployment Guide