Just an FYI for others who may have been / will be frustrated as we have been on one point...
Every time you create / modify a Lifecycle Template, one of the key activities is getting all the Transition check marks exactly right. We've been burned more than once from Windchill saving the Lifecycle template differently than we've configured it and carefully confirmed all Transitions to be - it adds additional checkmarks for Transitions (as well as additional workflow process mappings for Advanced Lifecycle types but that's another subject - see below).
I finally got frustrated enough to find the source - it's the properties copied below from wt.properties. No doubt some developer thought it was a good idea at one time -or more likely the developerwas following the direction from those defining required behavior. Don't know - maybe these have been there since Windchill 1.0, but these few propertiescan cause a great deal of havoc. We're planning on removing them on production and all future test / development installs of Windchill (and we will carefully note if these change in future releases, watching for others that sneak in). I can only assume that no one at PTC is aware of these being there.
These are the Properties in wt.properties that cause the automated Transition checkmarks to be populated:
- Population happens on Save at times, after you've carefully confirmed all to be the way you want it - doesn't show up until you Check in and View the result)
- In addition, the logic is just WRONG. One doesn't ever want to be able to promote all states to all states, including a state to itself, and Revise from the first state to itself doesn't make sense most of the time.
wt.lifecycle.transitions.default.PROMOTE=ALL
wt.lifecycle.transitions.default.REVISE=FIRST
Properties in wt.properties that cause the automated workflow process mapping:
wt.lifecycle.defaultGateProcess=Review wt.lifecycle.defaultPhaseProcess=Submit
