1 Reply Latest reply on Mar 26, 2013 1:22 PM by Brian Dalton

    Approval of Drawings made from a multi-configuration part or assembly

    Mitchell Kadel

      When submitting a drawing for approval via our ECO workflow, we attach the drawings we want to release to the workflow and proceed. When changing state, the vault will try to approve all associated files to the assembly from which the drawing is pulled.


      Currently we are unselecting all files that are not to be approved at this time, but this is tedious and time consuming.


      Is there another means of countering this issue? Does anyone have experience in dealing with this issue, or a similar issue?




        • Re: Approval of Drawings made from a multi-configuration part or assembly
          Brian Dalton

          This is the primary issue I've found with using ECOs that can control the release of more than one drawing/document.  Apparently, the out of the box ECO capability or EPDM is limited to those systems wherein each and every ECO releases one drawing -|- and each drawing requires its own ECO.  That's certainly a workable if clumsy method, but I've never worked in a company where this strategy was pursued.  It always makes much more sense to review and release related groups of drawings together, and that's the way we do it as well.


          The main problem stems from the fact that EPDM does not provide a mechanism for distinguishing between SW references (created as a result of components being inserted into assemblies) and EPDM references (created using Paste As Reference).  EPDM views them as identical, and so it can't perform a transition on referenced files without acting on all referenced files, regardless of how that reference was created or what it represents to you.


          AFAIK, there is no way around this limitation except through some sort of custom programming solution - except for using the one ECO per drawing paradigm.