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 -
If I understand correctly, you want to go into an Item and modify it (minor modification - just property changes, Designated User & Assigned Creator), without modifying the Release and/or Effective Date on the Item.
With the OOTB configuration and behavior of Product Engineering (PE), this is not possible, as you have discovered.
I am going to investigate more to see if there is anyway around it, but off the top of my head, this appears to be a behavior that you would need to modify the interaction of the Lifecycle and the Release/Effective dates or come up with some method code to accomplish. Any user interaction with the Configuration Items (Parts, Documents, etc.) is going to trigger a new Release/Effective Date because of the actual "change" to the item.
I am working on a solution that is outside the "OOTB" - stand by!
Lisa
Jared -
If I understand correctly, you want to go into an Item and modify it (minor modification - just property changes, Designated User & Assigned Creator), without modifying the Release and/or Effective Date on the Item.
With the OOTB configuration and behavior of Product Engineering (PE), this is not possible, as you have discovered.
I am going to investigate more to see if there is anyway around it, but off the top of my head, this appears to be a behavior that you would need to modify the interaction of the Lifecycle and the Release/Effective dates or come up with some method code to accomplish. Any user interaction with the Configuration Items (Parts, Documents, etc.) is going to trigger a new Release/Effective Date because of the actual "change" to the item.
I am working on a solution that is outside the "OOTB" - stand by!
Lisa
