However, a number of users continue to report the same symptoms using the fixed build (the fix was originally implemented in build 511, customer is currently running build 512). To recap the original problem, many users are reporting that they cannot connect to a ZMF Server instance from the ZMF4ECL interface, ChangeMan
This issue occurs if you have a Complex package which is linked to two participating packages from different Applications. When you expand the second participating package that is not from the same application as the complex packages application, in the folder view it does not display the components.
The "Approve" link is grayed out after an unplanned package is baselined. POST approvals cannot be done. POST baseline approvals should be allowed for unplanned packages.
The "Approve" link is grayed out after an unplanned/TEMP package is backed out to TCC status. POST approvals cannot be done. POST TCC status approvals should be allowed for unplanned packages.
A customer is reporting that since upgrading to ZMF 8.2 Patch 3 a number of their ZMF4ECL users are unable to connect to their ZMF Server started task at certain times. The failures to connect are linked
Users cannot connect to ZMF from the ZMF4ECL plug-in, because Web Services rejects the ENVIRONMENT LIST response because XJRJESTYPE is D in their environment. The Web Services definition only permits '2' or '3'. Any Character should be permitted in this field
