Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 27
Next »
Patch Name: AdeptiaSuite_6_5_02_28Nov_2016.zip
Build Tag: Release_6_5_02_28Nov_2016
What’s new in this release?
- 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.
- 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.
- Global Search
With this new feature, you can now search for any service from anywhere in Adeptia Suite.
- JDBC Drivers for Apps in Data Interface
Drivers for all the apps in Data Interface has been updated.
- 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).
- Support of query string in API Key
You can now pass API key as a part of query string.
- 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.
- 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
- 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.
- New Date-Format and Time Stamps in EDI Inbound/Outbound Relationship
New date formats and time stamps are added in EDI inbound/outbound relationship.
- Improved Log Cleanup
You can now delete data in chunks, while running log cleanup, from MySQL database.