cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Revise automatically changes the Lifecycle State to "In Work"

SOLVED
Participant

Revise automatically changes the Lifecycle State to "In Work"

Hi everyone,

We are using Windchill 10.0 M030

Whenever our designers revise a part, WTpart, or .dwg (ex A to B), Windchill automatically kicks the file's Lifecycle State back to "In Work" on the default template. We created our own custom template with the appropriate States, but this glitch is also even happening on test parts using the default template. Every time a part or dwg gets a revision, we have to reset the state for each file.

We haven't gotten the managerial PLM features integrated into company procedures yet, so for now this is just an annoyance for designers using Windchill. However, as we move forward, this could cause some serious problems and confusion.

Is there a preference somewhere to configure Windchill so that when revising, it maintains the same Lifecycle state and template? I cannot seem to find one.

Thanks

-Jon

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Revise automatically changes the Lifecycle State to "In Work"

Thank you everyone for your help,

I did end up achieving the behaviour that I needed, but I would like to clarify how:

Upon revise, the Lifecycle would revert back to the Basic template, regardless of how I configured it. So to solve the issue once and for all, I went to the Site level and edited the Basic template. I changed the States and added checkmarks for the Revise transition of each state, with each checkbox the same as its state. This is only possible at the Site level utilities.

We will change all parts on our server to the Basic template, and everything should be good from here on out.

-Jon

15 REPLIES 15

Re: Revise automatically changes the Lifecycle State to "In Work"

Lifecycle transition for REVISE at the current state is set to go to INWORK? Please check at transition tab for this lifecycle.

Re: Revise automatically changes the Lifecycle State to "In Work"

Jon

You may configure the state change for new revisions as you please, but you can hardly call the default setting a "glitch"?

To me it makes perfect sence that the new revision automatically moves to "In Work" state.

Please try and explain your lifecycle states and revise logic, this way we can help you in the right direction.

Hugo

Re: Revise automatically changes the Lifecycle State to "In Work"

This is what the Transition tab looks like for each state of the lifecycle, but I'm not sure exactly what the effect of these checkboxes are:

Transitions.jpg

Re: Revise automatically changes the Lifecycle State to "In Work"

The way our revision system works, reverting back to the first lifecycle state (let alone the default template) when revising would break procedure.

For example,

Concept phase, rev stays at A.

Design phase, revs begin changing (A,B,C) as quote drawings are revised.

Procurement phase, revs continue to change (D,E,F) as tooling drawings are revised.

Production phase, revs continue to change (G,H,I) as production drawings are revised.

Thus, when a drawing or part is revised, we would like both the custom Lifecycle template, and state to remain unchanged.

Jon

Re: Revise automatically changes the Lifecycle State to "In Work"

Jon

I think you may be missunderstanding the concept of states and how they relate to revisioning.

The general idea is that each revision of a document would go trough the same or similar chain of lifecycle states.

Example: "In Work"->"Checked"->"Released"

In your example, a document would have to be revised when it is used in each state, even if the document it self was not changed.

In my opinion, thats not a good idea.

In your example i guess you only need to remove the transition checkbox for revise entierly and the document would stay on the same state after revise (however, im not a Windchill admin so i can not say that for sure :-)

This is a very interesting topic so if others have any views on this, please join.

Hugo

Re: Revise automatically changes the Lifecycle State to "In Work"

The online help for lifecycle templates, and specifically for transitions, might be useful to you. The topics entitled "Example of Defined Transitions" and "Transition Rules" seem relevant to your questions. I've linked to the topics in the 10.0 M030 Windchill Help Center available on ptc.com.

If you have any feedback about the lifecycle (or other) Windchill documentation, I'd like to hear from you.

Thanks,

Jane

Jane Zupfer
VP, Windchill Publications
T 763.957.8299 E -

Re: Revise automatically changes the Lifecycle State to "In Work"

Jon,

WHen the REVISE occurs you want to stay on the same lifecycle state. In your screen shot, when you are revising in CONCEPT state, the part will remain at the CONCEPT state.

Similar way you should check the transitions on other states, just set the Transitions REVISE checkmark for the SAME state. That will solve your problem.

Preeti

Re: Revise automatically changes the Lifecycle State to "In Work"

Probably it is a good practice if the part is revised it should change the lifecycle state to INWORK or Working state.

You might have issue giving permission to modify at Released state. In my view it should be restricted.

Windchill support your use case however it may not fall under "Best Parctices".

Re: Revise automatically changes the Lifecycle State to "In Work"

Thanks for the tip Preeti, but unfortunately this did not change the behaviour.

After checking these boxes appropriately for each state, the revise command does indeed keep the same state in the "new state" field of the confirmation dialogue box. However, once you press OK, the part reverts to the Basic Lifecycle template again, in the "In Work" state.

The problem persists, as every time we revise an object, we must reselect its lifecycle template and state.

Also, in case this helps, I do have administrator priviledges for Windchill. We are a small company and attempting to configure this on our own, so myself and my supervisor are taking on this challenge. We are mechanical engineers, so some of the more complex configuration methods have been difficult for us to learn.