AnsweredAssumed Answered

Understanding Revision Counters

Question asked by Jim Sculley on Mar 18, 2010
Latest reply on Mar 23, 2010 by Jim Sculley

Can someone explain the interaction between the 'Increment Revision Command' feature of the State properties and the 'Change Revision Counters' feature of the Transition properties? My interpretation is as follows:

 

1.  The 'Increment Revision Command' feature controls the revision that will be applied to a file entering the state via a transition with an 'Increment Revision' action.  If no transitions entering this state have an 'Increment Revision' action, then there is no reason to choose anything other than '<None>' in the 'Revision Number to Use' drop-down list.

 

2.  The 'Change Revision Counters' feature controls the way the 'Increment Revision' action of a transition will occur.  If the transition doesn't have an 'Increment Revision' action, there is no reason to touch these settings.  If the transition has an 'Increment Revision' action, but the increment isn't special in some way (i.e. resets one component of a multi-component rev number) there is no reason to touch these settings.

 

3.  If a transition uses the 'Change Revision Counters' feature, it supersedes the settings in the  destination state properties.

 

I will assume my interpretation is incorrect, because I'm seeing some behavior that doesn't make sense.

 

I have two revision numbers:

 

Pre-release with a single letter

Standard - a number and a letter (the letter is typically absent but sometimes required at certain points in the workflow)

 

 

I have a workflow that looks like this (states denoted with S, transitions denoted with T):

 

==========================

S: Work In Progress (Rev Number to Use: <None>)

 

T: Submit for Release

 

S: Release Pending (Rev Number to Use: <None>)

 

T: Release (Automatic)

 

S: Approval Pending (Rev Number to Use: <None>)

 

T: No Approval Required (Automatic with Increment Revision Action)

 

S: Approved (Rev Number to Use: Standard, Letters: Reset to 0, Numbers: Increment by 1)

 

T: Change Requested

 

S: Changes Pending (Rev Number to Use: <None>)

 

T: Submit Changes

 

Goes back to

 

S: Approval Pending

=======================

 

If I create a new drawing, check it in and perform the Submit for Release transition, the files moves to the Approved state, as expected, but the revision number is 0A, which is not expected,  Why did it ignore my settings (Reset Letter component of rev number to 0) in the destination state (Approved)?

 

If I perform a Change Requested transition, followed by Submit Changes, the file returns to the Approved state and the revision is now 1, as expected.  All subsequent change requests bump the rev appropriately as well.  Only on the first time through the workflow does the letter component appear.

 

Also, if I send the file from Work In Progress through our review workflow (which uses the Pre-Release rev number) and then do a Submit for Release, the file goes to Approved with the correct revision number 0.

 

If I set the state properties on Approval Pending to use the Standard revision number, with the number component incrementing by 1, then it all works as expected, but this violates item #1 of my interpretation since there are no transitions into Approval Pending that include an Increment Revision action.

 

The admin guide and training guide do not describe the interaction between these two features, so if someone has a clear understanding of this, I would appreciate some enlightenment.

 

Jim S.

Outcomes