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

Provide a supported way to update existing versioning schemes that are in-use

Provide a supported way to update existing versioning schemes that are in-use

Currently, PTC does not support modifying existing versioning schemes (i.e., File-Based/State-Based) once they are in-use in Windchill It may be possible to safely add versions to the end of existing schemes, but if the versions need to be inserted anywhere into the middle of the scheme then there is no supported means PTC provides to do that. This becomes a problem as company requirements change over time (organizations/companies change or merge, systems are consolidated, data from other systems is migrated/merged into an existing Windchill system, business practices change, etc.). There should be a supported utility or set of supported utilities or a supported set of steps that customers can safely follow to allow them to insert new versions into their existing versioning schemes, as required.

1 Comment
mwaite
Regular Member

Hi Lori,

We change our file base versioning scheme every time we buy another company or a new customer introduces new version labels.

We just follow the rules as described in https://www.ptc.com/en/support/article?n=CS30667 ( which clearly says it's not supported ) and then use the process described in  https://www.ptc.com/en/support/article?n=CS22606 to fix the sort ids.

 

Is your suggestion to remove the "not supported" statement from the article or were you asking for a new tool / methodology to manage the version labels?

I could get behind your idea if I knew what you were proposing and how it would be different from the tools we use today.

Michael