Skip to main content
B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
August 29, 2019
Solved

select revision at revise

  • August 29, 2019
  • 3 replies
  • 2413 views

When creating a versioning scheme in Windchill 11.0 m030, we have the need to jump versions.

We initially create parts/documents at version A. These get revised to new versions up to a point where we decide to jump the version to version 0 for a production release. When I select the file for a Revise action, I am only getting the next version in my version table. It will not let me change the version to the numeric sequence in my version file.

What do I need to set to get the revision box to allow me to select my next revision?

Best answer by MikeLockwood

preference: Allow Override On Revise

3 replies

M
22-Sapphire I
MikeLockwood22-Sapphire IAnswer
22-Sapphire I
August 29, 2019

preference: Allow Override On Revise

B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
August 29, 2019

Mike got me the answer to allowing the version selection, but for some reason it is not allowing me full access to the versions I have loaded into Windchill. The default version for a new document is A, that is fine. When we revise, we may jump to 0 as the next version, but I can only enter alphas.

When I extract the version table, it is StateBased, the first version seed MILSTD at A and goes through AY. Then we have a seed NUMERIC which goes from 0 to 99.

Do I need to load a different versioning rule file?

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
August 29, 2019

PTC User presentation way back in 2007 was on this...

Revisions in the statebasedversioning.xml file have to organized in "seeds" (and loaded to the database).  Have to verify the database using -read for the load command.

 

Revise transitions in the lifecycle template have to be set up to Revise to the next seed that contains the desired Revision. OTB this is "NUMERIC" and "MIL-STD" for numbers, then letters.

 

Lots involved - complex.

Terms & ConditionsAccessibility statement