version scheme

[Markh74]

Good day

Does anyone have an easy to understand guide with pictures on how the versioning scheme works in Windchill that I can use to explain.

We are using the standard OOTB version A.1, A.2.....B.1, B.2....

The users are asking the following questions.

1.) How do we know that the version we see, lets say A.4 is the last correct version of a document

2.) If the Document is on a B.1 does that mean it is a newer version that A.4

[avillanueva]

https://support.ptc.com/help/wnc/r12.0.2.0/en/#page/Windchill_Help_Center%2FObjRuleObjectVersioningOOTBDefaultScheme.html%23

Does this help?

1. Version schemes are ordered and the scheme you are using is based on this:

https://support.ptc.com/help/wnc/r12.0.2.0/en/#page/Windchill_Help_Center%2FObjRulesChp_StandardAlphScheme.html%23wwID0EBF4V

2. Yes, B.1 is later than A.4. What is before the period is the version which has an order defined by the scheme chosen. Those are defined in the wt.properties file and called out for objects in the object initiation rules files.

There are other schemes. Integer based (like what iterations use) and Milspec.

You can also create your own series using File based schemes. For your OOTB setup, it handles cases like what happens when you get to Z? It moves to AA and then continues to AB, etc.

[BenLoosli · Accepted solution]

One added note: any .1 iteration is equal to the prior revision's last iteration. So your B.1 is identical to the A.4, except it has been revised for changes. When the first changes are made, it will become B.2 upon check-in to Windchill.

[MikeLockwood]

One addition added note.

When you Revise, the system actually uses the same file(s); no new content is created.  So, Revising A.3 to B.1 for example results in the same file(s) for B.1 as are in A.3.  

[HelesicPetr]

Hi @MikeLockwood and @BenLoosli 

Additional note>

If an user revises directly in the Creo, where the change design has been made, the version B.1 becomes the latest changed one and is not same as A.4. 

PetrH