Hi there.
We have a series of Documents that we need to make a minor change to - edit the "Assigned Creator" or "Designated User". We wanted to use the Manual Change lifecycle state to achieve this, but after promoting an item into Manual Change, editing, and attempting to promote back to Released, we get a InvalidEffectiveDateValueException "The value of the effective_date property specified for the Document is invalid. A value is required and it must be greater than or equal to the today date.". But we would like to keep the original prior effective date.
When saving the edit while in Manual Change, we can see that the Release Date gets cleared. So perhaps attempting to promote back to Released when there is no release date set is causing the effective date to get checked?
So: 1) Is using Manual Change the correct approach to making a minor edit, such as changing Designated User? 2) How can we get Manual Change to work without causing the released and effective dates to get updated to today?
Using v11 SP 12. Thanks!
Jared -
Yes, the MCO. The MCO is meant to allow you to change the related ALM list without changing the related part's revision or effective date. In that case, you aren't actually changing the related part or internal part at all, you are only changing the relationship(s) of that part to Manufacturing Parts, that's why it works the way it does. And, unfortunately, as you have discovered, that does not translate to making changes to the Part Item itself.
Sorry!
Lisa
Jared -
Yes, the MCO. The MCO is meant to allow you to change the related ALM list without changing the related part's revision or effective date. In that case, you aren't actually changing the related part or internal part at all, you are only changing the relationship(s) of that part to Manufacturing Parts, that's why it works the way it does. And, unfortunately, as you have discovered, that does not translate to making changes to the Part Item itself.
Sorry!
Lisa
