2 Replies Latest reply on Dec 7, 2010 10:11 AM by Jeremy Schmidt

    mimicking revisions with "Change Revision Counter" in transitions

    Jeremy Schmidt

      I have read through several posts with similar issues, but couldn't find exactly what I'm looking for.


      First, a little background... our revision scheme is as follows: we have both minor and major revs. Majors are 00-99 and minors are 00.A, 00.B, ..., 00.Z. So the first minor rev after 02 would be 02.A. The next minor would be 02.B. The next major would be 03. The next minor would be 03.A (NOT 03.C).  I have successfully setup this schema in our workflows.


      My issue is this... we may have a legacy document that exists at revision 01.B and has a revision history of 00, 01, and 01.A.  If a user adds another document with the same part number, we need that new document to start at revision 02.B.  We do not want to show this revision history (revision flags) of 00, 01, and 01.A, because in reality, the document did not exist at these revisions.  Instead, I would like to "silently" increment the revision level.  I have a fairly complicated workflow setup that mimics our normal production revision process, but uses the "Change Revision Counter" option in the transitions instead of the "Inc. Revision" action in the transition.  Basically, there is a state and corresponding transition for a major and a minor revision and the corresponding revision is incremented at the transition.  So for my example above, the document would go through the major transition to increment the major revision counter by 1 (rev 00).  Then it would go through the same transition again to increment the counter again by 1 (rev 01).  Then it would go through the minor transition twice to increment the minor counter by 1 each time (01.A, 01.B).  The document is then pushed back to the production workflow.


      Now let's say that I send both documents through the standard workflow and go to the next major revision (rev 02).  This works great.  However, if I were to go to the next minor revision instead (rev 01.C), the revision is incremented to 02.C, not 01.C.  I believe that it has something to do with the values in the "Increment" field in the "RevGenCounters" table of the database.  My existing document has different values than the new document before I even send the document to the normal production workflow.  It appears that the "Counter" field and the "Increment" field do not operate in the same way if the "Change Revision Counter" is used to increment the revision instead of the "Inc. Revision" action.


      Any insight or suggestions are much appreciated.  Thanks for your help.

        • Re: mimicking revisions with "Change Revision Counter" in transitions
          Frank Pampreen



          That’s a pretty complex setup you have their.  We have had customers with similar issues and have written an add-in that I think would simplify this quite a bit.  Take a look at our Bump/Jump add-in and see if this might help out your situation.  To keep the video brief there are a lot of options on controlling the revisions that are not included. However, it does handle multiple revision component schemes and is activated through a transition or manually via a right mouse button menu.   If you have any questions feel free to contact me directly at ftp@capinc.com




          Frank Pampreen

          Computer-Aided Products, Inc.

            • Re: mimicking revisions with "Change Revision Counter" in transitions
              Jeremy Schmidt



              I was blocked from your site, but will take a look from home tonight.  However, I would prefer to work this out without a separate addin.


              I think I figured out the issue, but don't know how to work around it.


              If I send the document through the normal Major workflow to get to revision 00, the "Inc. Revision" transition action sets the "RevGenCounters.Counter" field to "0" and the "RevGenCounters.Increment" field to "True".


              0, true (rev 00, flag) => all makes sense so far


              But if I use the "Change revision counters..." transition option instead, it increments the "RevGenCounters.Counter" field to "1" and leaves the "RevGenCounters.Increment" field at false.


              1, false (rev 01?, no flag) => I don't know why it doesn't start at 0, but at least it still makes sense


              So if I do this "silent" major revision and then go back to the normal minor revision workflow, the major (numeric) revision component is one value higher than I need.


              1, false (rev 01, flag) => still makes sense


              So you might say that I should then just use the "Change revision counters..." transition option to reset the major component to "0" for the first rev.  Makes sense, but...


              If I go to the normal major revision workflow instead of the minor workflow, the Inc. Revision" transition action leaves the "RevGenCounters.Counter" field at "0" and changes the "RevGenCounters.Increment" field to "True".


              0, true (rev 00, flag) => This what I really don't understand.  Why doesn't it increment the counter field so that it's 1, true (rev 01, flag).


              I hope that made some sense.  I can adjust the options to get it to work for either the next real major or real minor workflow, but I can't get it to work for both.