I'm setting up Change management in Windchill which broadly seems to be logical and straightforward, except I'm stuck on one bit.
When a user receives a task to make a change as part of a change activity the part doesn't appear to release to enable the checkout and revise or check out, change and then check in. In the test example i'm using, the part is in a 'Released' state as this is the state we will want to be using change control in, and the lifecycle in that state has 'change' and 'revise' ticked (although revise isn't allowed by the access rules for those users in that state). Presumably I shouldn't be allowing the engineers to normally be revising in this state as this would defeat the object of having a change system?!. I'm missing a key point somewhere, i've hung onto the assumption that 'change' in the lifecycle enables the part to be changed by the assigned user without further permissions, but maybe that's wrong?. The part does have the 'pending change exists' flag so it looks like it ready to be changed and all change admin have completed thier actions up to that point. I'm using Windchill 10.0.. Any help appreciated. Thanks