How does Version Series in Lifecycle Administration work?

[mmutyala]

Specifying Controls to 'Numeric Series' or 'Alpha Series' of WTPart or WTDocument etc., So that Users can Set-State, Read, Download, etc., in those Version series only.

Is this possible by Version Series Tab in Lifecycle Administration and How does this really work?

[slapha]

The version series listed in lifecycle administrator is for statebased versioning.  With multiple lifecycle states you can have it change series from one state to another.

A typical example you can have a prototype/concept stage that uses numbers so you can have multiple conceptual revisions, and once the design is approved for production or core design it could be transitioned to a production or design lifecycle with letter versions. The object will then keep the letter versions going forward as the design progresses.

I think one of the out of the box workflows usually has an example of this.

[MikeLockwood]

Almost impossible to understand how this works without some diagrams.  Showing Revise on the diagrams going from one Revision to another on a two-dimensional diagram helps greatly.  Revise when configured to the same "seed" (e.g. Numeric) goes to the next Rev in that seed (e.g. from Rev 2 to Rev 3).  Revise from a Numeric Rev to MilStd jumps to Rev A (or possibly Rev -). Almost everyone in fact uses Numbers and then Letters or Letters and then Numbers or some variation for Rev's it seems, and state-based versioning is a great way for Windchill to accommodate it.  But - It's tricky understanding how to set it up.  Good diagrams help a lot!!