I'm having some problems setting the revision scheme to how we'd like it. It is currently set that when a product is initially developed it can be checked in on the primary revision of A - Z, when the product is ready to be released it goes to the secondary revision scheme which is numeric. However if issue 01 needs further work we can set it back to WIP and it can be checked in with a working copy symbol ( + in our case). However, every time any work is done to a previously released product and checked in at the next working copy it always overwrites the pre-checked in working copy, so you check in the modified 01 at 01+ then if you work on it and check it in again it stays at 01+ overwriting the existing 01+ etc. till it is released at the next numeric revision i.e. 02.
What I'd like to achieve is:
Prototytpe/Concept work to be checked in at alpha ( A - Z)
Released Product at a Numeric value (01-99)
Updates to released products to be checked in at Numeric Alpha (i.e. 01-A, 01-B)
until ready for next release where it will go to 02.
I can get close but just can't get to get it to do exactly what I'm after. Any help greatly appreciated.
Thanks
I don't have a lot of experience with custom revision schemes, but I think I know how you can accomplish what you want. It would all be set up in the "Revision Scheme" tab in the PDM VaultAdmin tool. Below is a screenshot of my settings.
I think what you can do is set up your primary revision to use a Listing, rather than Range. In your list you would enter:
A
B
...
Y
Z
01
02
03
...
Then you'd want a "-" separator, and in secondary you could use a Range from A to Z.
Now when you initially check in a project it will go to A-A. I don't know if having the alpha secondary revision along with the alpha primary prototype revision is a deal breaker for you, but maybe you'd be ok just ignoring it. Anyway, as I was saying initially a project would have A-A, then the next check-in could be B-A, then C-A etc. while you are in prototype stage. You'd just need to make sure the peopel checking in the documents are bumping the primary revision at check-in rather than the secondary. So it should go from A-A to B-A, not to A-B. Once you reach initial release you can check it in and force it to 01-A. Any WIP changes can bump the secondary revision (01-B, 01-C), and any official changes would warrant bumping the primary revision to 02-A. I hope that all makes sense.
The weirdest part of that scheme is the primary and secondary during prototype stage. I don't know how set in stone your scheme is, but I'd like to suggest maybe you can just set up your scheme with primary from 00-99, and secondary from A-Z. Then have all of your pre-release check-ins use the 00 primary and increment the secondary. So 00-A, 00-B etc would be pre-release versions. Then on initial release you'd move to 01-A and go from there.