2 Replies Latest reply on Aug 12, 2010 6:46 PM by Joel Magnuson

    Workflow States

    Barry Stump

      OK we want to set our workflows up so that we "Release to the Library" (state).  And from that we will have a "Issued for Production" under a workorder or job number.  This will ask for and then fill out field varaibles on the drawing to make the drawing work order specific.  Ok that is not a big deal to accomplish.  Move it to the "Issued for Construction" state, do the variable changes, generate the pdfs, dxfs, etc, then send it back to the "Released to Library" state.  Ensuring when it gets back home all the variables are as they were.

       

      But what if the drawing is "Under Revision" and the shop wants to issue the old one for production.  Can we move an old revision thru a state change while a newer version is under a different state chaange?  Can the "Issued for Production" branch be a dead end line that does not change the original?  If it does truly touch the metadata (as I am sure it does) is this even possible?  If not what are the drawwbacks for forcing the shop to wait for the revision to complete?  Timing I am sure.

       

      I think the answer will be that it is best to just have the shop wait for the revision or the cancel the revisions temporarily.  If they wait I would have to have EPDM notify the person responsible for the revision that that shop needs the drawings ASAP.

        • Re: Workflow States
          Jeff Sweeney

          No, a file may exist in only one state at a time. Thus older versions may not move independent of the latest version.

           

          What a great enhancement this would be!

            • Re: Workflow States
              Joel Magnuson

              This isn't entirely correct.

               

              Older revisions/versions cannot move states independently of the latest version because older versions/revisions cannot move states at all.  When a file is released and stamped with a revision, it's fixed in that state.  However, if you attempt to change the state of version 4/5 for example, it will move version 5/5 (or the latest version), not 4/5.  However, in EPDM 2011 I believe they have added a tool to move all versions at the same time.  I think this is used to get old versions out of a workflow.