Not sure of solution without knowing more of the setup. But I have seen some stuff like that... One thought, both Transitions and States have an "Increment By" setting on the Revisions - try switching which one is adding 1 (leave the other blank).
There are probably some ways you could reorganize your workflow that would help, but hopefully still get the desired effects. Perhaps change the Intial State checkbox for new files.
I also wonder why you would increment the EPDM revision on a new file, or a file in the Initiated state. I believe that is an usual approach, but you may have good reasons for it. Most would only set the Card Revision Variable to the first value - before the change is finalized.
Your way everything you add is immmediately stamped as a Revision, even if it turns out to be junk that never advances. What is your final "Released" type state - and what are you doing there? Incrementing Revision again?
Basically Brian. i have cases where i can't get anyone to follow a set of rules to set the revison a file. I tell them over and over again that the Solidworks Revison Property "Revision" is not the controlled revision. Enterprise is the controller of revisions.
This way i can give them a simple command to increment the revision and it takes care of setting the Solidworks "Revision" property along with a few other properties.
I have so many cases where they will do work, not set the Enterprise Revision, and now the revisions are all messed up. i could change the initial state to have an automatic transition to set the initial revision, but i still have legacy files to import.
I got the answer from My VAR today. all i had to do to eliminate the skipping to revision 2 was to delete the "Increment By" values in the transitions and setting the increment by value in the initiated state to 1 so the transitions inherit the value from the next state if the "Increment by" value in the transition is blank.
The final Released state Does not increment the revision. It transitions to The Released to Production Workflow. The workflow in discussion is for prototypes.
so basically the fix was to remove the "Increment by" value in the transition, and add it to the initial state.
Interesting, thanks for explaining.
Of course I don't undestand your whole situation, but I still imagine you could set the EPDM database Revision ("Local Revision") at some later state, when work is actually happening based on the design (making a prototype or being sent to some outside supplier or whatever). Database revisions are typically added when a file is moved to a protected state where it cannot be changed (until transitioned back to some Edit state). I guess that is what bothers me. This is also significant if you use Cold Storage.
On the other hand the Card Revision is often initialized at the beginning (with Set Variable action, or with a Default value set on the data card).
As you already know the user doesn't have to remember to do it, if it is part of the transitions they must put it through. You are bumping the database revision automatically at the beginning (Initiate New Revision), when the file can be changed, but then is it meaningful? Could it be bumped automatically a bit later?
Just sharing some ideas.