Windchill Document Version system configuration changes

[mprasad]

Hi,

Current Document Version system is as below

First Check in: -A.1 (In Work)
Iterate: -A.2, -A.3 (In Work)
Revise: B.1 (Released)
Iterate: B.2, B.3 (In Work)

I'd rather want to do this:

First Check in: -0.1 (In Work)
Iterate: -0.2, -0.3 (In Work)
Revise: A.1 (Released)
Iterate: A.2, A.3 (In Work)
Revise: B.1 (Released)
Iterate: B.2, B.3 (In Work

Please HELP.

Thanks & Regards

Manish Prasad

[kpritchard]

Manish,

Have a look at State Based Versioning to accomplish something at least close to what you are looking for in switching from a Numeric to Alpha versioning scheme.  I have looked at SBV and have considered it but not implemented because the system required events and timing to support SBV did not fit with the process.  If you need the "-" characters, you will need to look at a file based versioning scheme which I have used for a numbers mean "x" and alpha means "y" approach to revision levels.

You may need to adapt your expectations somewhat on the Revise Action though... A.X (Released) will go to B.0 (In Work) when Revised.

[BhushanNehe]

Manish,

As mentioned by Keir, StateBased series should help in achieving your requirement. You can refer to help center for more details.

http://support.ptc.com/cs/help/windchill_hc/wc102_hc/index.jspx?id=ObjRulesChp_XMLVersionFileLoad&action=show

You can define in Lifecycle admin to use Numeric series in InWork state and Alpha series in Release state.

Regards,

Bhushan

[MikeLockwood]

Simple diagrams greatly help this discussion and related decisions (and system configuration testing and user training).

It really helps to put each Revision on a separate line and list all of the states horizontally, then the arrows between states, either at the current Revision or a new Revision become the transitions that you're deciding on.

The whole point of state-based versioning (which many people don't get the value from) is having different transitions between the states used for numbered Revisions vs. those used between states for lettered Revisions.

There are multiple ways to "make the leap" from the last Number to Rev A, all of which have pro's and con's.

Work backward from what you want various groups (or Roles) of users to be able to do at number Revisions and at Letter Revisions, and what type of business process needs to surround going from numbers to letters.

[mprasad]

I am redefining my question here once again

Current Document Version system is as below

First Check in: -A.1 (In Work)
Iterate: -A.2, -A.3 (In Work)
First Release : A

First Revise Iterate : B.1 (In work)
Iterate: B.2, B.3 (In Work)

I'd rather want to do this:

First Check in: -0.1 (In Work)
Iterate: - 0.2, 0.3 (In Work)

first release :- 0 (Released)
First Revision Iterate : A.1 (In Work)

First Revision Release : A (Released)

Second Revision Iterate : B.1 (In Work)

Second Revision Release : B (Released)

so and so forth...

Please guide..

[BenLoosli]

All files will have an iteration number attached, no way around that.

The version 'name' is made up of the revision and the iteration.

You just need to set your revision table so the -0 revision comes before the A revision.

First Check in: -0.1 (In Work)
Iterate: - 0.2, 0.3 (In Work)

first release :- 0 (Released)
First Revision Iterate : A.1 (In Work)

iterate - A.2, A.3, etc

First Revision Release : A.x (Released)

Second Revision Iterate : B.1 (In Work)

Second Revision Release : B.1 (Released)