Envoy 2.5 Released

Betta Fish

O_ValInt_JDE_E1_clrEnterpriseOne 9.2 has arrived!  Envoy sailed through OVI certification last month but we wanted to pack more into the last quarterly release of 2015.  Our Christmas gift to you.

Enhanced error reporting and SQL server, Oh my.

  • Multi-foundation is always a good idea when working through a tools upgrade.  A new hint has been added to the build report to point out when Envoy is run with the wrong JDENET port.
  • The JDB_OpenTable API does not treat all databases equal.  Ask B9698711 for a record count when the physical table columns do not match specs. SQL server will always return zero while Oracle returns a number. Our Table Generation module has been revised to work around this JDE feature.

You can download the latest version of Envoy in the support portal at our 2.5 downloads page, and for more details about the changes that made it in, see below.

Release Notes Summary

v2.5| December 2015

New Tools 9.2 Support
Web OMW projects, introduced in tools 9.2, will be excluded from pickup as these objects do not require a package build.  Software package build header/detail structure has been revised to accommodate changes introduced in 9.2.
Enhancement Version Number
The Envoy version number is now displayed in the build report header.
Enhancement Multi-Foundation Error Reporting
When operating in a multi-foundation environment it is possible that Envoy cannot obtain the full package name.  This occurs when the workstation is operating on the incorrect JDENET port. This hint has been added to the error message displayed on the Envoy build report.
Bug Fix Duplicate Key Error in Client Deployment
Envoy produced a duplicate key error in instances when the same full package was deployed to a client multiple times. This has been addressed.
Bug Fix Complete with Warnings
In certain instances, notification email was generated with the subject line “Envoy complete with warning(s) in table generation” when no warning condition exists.  This has been corrected.
Bug Fix Inaccurate Record Count
A zero record count was reported on SQL Server databases when the number of columns in a physical table did not match specs.  This has been corrected.