A revision controlled object such as a WTPart can be matured through several lifecycle states WITHOUT iterating the object. This of course can only be enabled by the states and transitions defined in the lifecycle. For example the LC: Create | Engineering Released | Released. This LC has a change transition "Engineering Release" defined to mature an object from Create to Engineering Released. Additionally a change transition "Production Release" to mature an object from Engineering Released to Released. Therefore it is possible to first execute the change process for WTPart@A.13 which will mature it from Create to Engineering Released. Then execute another change process which will mature the SAME iteration (A.13) from Engineering Released to Released. Now there are 2 Change Objects linked to A.13 and 2 LifeCycle History records. Which Change Object resulted in which LifeCycle History object?
In Windchill 10.1 M040 it is NOT possible to determine the answer to this question other than some loose date/time comparisons. I propose a "link" or some other method by which a user can more accurately determine which Change Object drove the LifeCycle History records. This is important for Steelcase because we are recording "Is/Was" comments on the link between the changeable (WTPart in this case) and the Change Object. Then we have a report that shows the comments of what changed throughout the LifeCycle History of the changeable. This report includes the Revision and State of the changeable. Since a link is not present in Windchill we have to write a "loose" date/time comparison.
4 Comments
