Forum Discussion
Former_Member
9 years agoAccelerator III
Expanded my test on this a bit. I had created my own version of PE_CreateNewRevision . To test the behavior, I went back and modified PE_CreateNewRevision by removing the check for revision status.
// Item must be in the Released state //if (!isInReleasedState) //{ // return inn.newError(CCO.ErrorLookup.Lookup("PE_ManualRelease_MustBeInReleasedState", thisType)); //}I then used this method on my Model objects. When the model is in a state that PE_CreateNewRevision sees a released life cycle state ("Released") it increments the Major Revision. If the model is in a life cycle state that PE_CreateNewRevision would see as a non released part (with the code above not commented out), it fails to increment the Major REeision. Its looking like the the items this.apply("version") has begun looking at the items "State" to determine if it should increment. Whats also off here is that its not looking at the item's lifecycle state "released" status. Each life cycle state has a "released" check box. current_state is shown as a referenced item type, specifically "Life Cycle State" item type. I wanted to know if the "released" property of the life cycle state item was available to be checked. I added a foreign property to my item, referencing the Life Cycle State item and using its "is_released" property. When viewing this property in a form, there is no update. When accessing my "life cycle state" items from a TOC view, the "is_released" property is correct.