Customer receives messages: CHANGES WILL BE LOST and COMPONENT OUT-OF-SYNC when trying to edit and stage a backed out component. This is when the VALIDATE VERSION DURING STAGING parm is equal to YES.
In ZMF, if a baseline component has changed since you checked out the component in your package, when you attempt to edit the component get ‘ CHANGES WILL BE LOST ’ and the long message ’CMN2556A - Check out new version from baseline; changes will not be saved.’ In ZMF, when staging (BUILD) the same component you get ‘COMPONENT OUT-OF-SYNC’ and the long message ‘CMN2555I - The baseline version of ABC101.SRC has been modified’.
When checking out components from promotion various methods work differently with relation to further edits, 'validate version during staging' processing and the following error: CHANGES WILL BE LOST /CMN2556A - Check out new version from baseline; changes will not be saved. The processing varies between releases, too. Attempts to edit a component after checking it out from promotion in an application with VALIDATE VERSION DURING STAGING ===> YES in ZMF 5.6(.3) result in the following:
Validate Version during staging is set to Yes They perform a batch checkout of a component that does not have baseline stats. If they try to edit the component, they receive " Changes will be lost ". “CMN2556A - Check out new version from baseline; changes will not be saved.”
It is possible to edit the text field defaults of a checked in field within composer. These changes will be lost on check out of the field in question.
Whilst resolving this issue it became apparent that the underlying cause may also result in missing " CHANGES WILL BE LOST "/"CMN2556A - Check out new version from baseline; changes will not be saved." messages during component staging processing. These messages should be issued when there is a possibility of change regression and the 'Validate version during staging' option is enabled in application admin.