2/24/15 Update:
If I check "Allow latest revision overwrite" on the Vault Settings tab the revision changes correctly for both drawing & part - both go to A.01.
However, I do not want to allow latest revision overwrite.
======================================================================================================
I have a PDM Workgroup vault set up with very simple revision and lifecycle schemes.
During the transition between lifecycle statuses the revision does not advance automatically using the correct scheme.
My vAR has been unable to tell me if the vault behavior I desire is possible to configure.
My revision scheme has a primary of -, A, B, C... and a secondary of 01, 02, 03... (the last revision type is set to optional).
I have two lifecycle statuses - In Design and Released (lifecycle tab settings below).
My workflow is as follows:
Documents are first checked into the vault in an In Design status and at rev -.01 further check ins increment the secondary revision, -.02, -.03...
When a document is Released the revision goes to A
When a Released document is modified it moves back to In Design and the revision moves from A to A.01
Further check ins increment the secondary, A.02, A.03...
Finally, when Released again the revision goes to B.
Here is what happens in SW using the PDMW interface on the task pane.
Starting from part & drawing Released at rev A
Check out & take ownership of both
Change something on both
Save both
Check in
Check in active document (drawing is active) - picks up drawing & part
Status automatically goes to In Design for both
Revision on drawing automatically goes to A.01
*** Revision on part goes to B (incorrect & unexpected) why not A.01?
Workaround is to now manually edit revision on part and set it to A.01
Subsequent check in
Both rev's will automatically go to A.02, A.03, etc
Release
Check in active document (drawing is active) - picks up drawing & part
For both manually set status to Released
*** For both revision automatically goes to next secondary A.04 (incorrect & unexpected) why not B?
Workaround is to now manually set both revisions to "next primary revision"
Ownership is automatically given up
--------------------------------------------------------------
Lifecycle Tab (listing checked options only)
general - enable lifecycle
In Design status
allow status changes on check in and...
selected in the check-in dialog box
administrators
document owner with RW access
this user or group - none
change the document owner to - do not change
change other document revisions... - do not change
when a document at the selected... - do not change
secondary
Released status
allow status changes on check in and...
selected in the check-in dialog box
administrators
document owner with RW access
this user or group - none
change the document owner to - none
change other document revisions... - do not change
when a document at the selected... - In Design
primary
secondary