2 Replies Latest reply on Jul 5, 2012 7:36 AM by Dennis Hvam

    Can EPDM automatically change state upon file move?

    Mark Lauritzen

      I have set up a Concept folder structure as a "playground" for our engineers to let their creative juices flow freely and is not under Configuration Management (CM) control. This folder structure has its own workflow, with a single non-releasable state. If a file is created within this folder structure, it automatically starts in the correct concept state.

      If a file is created in the production folder structure it automatically is assigned a production WIP state and is managed by CM.

      If a file is created in the production folder structure but should have been in the concept folder structure it can easily be moved by the engineer as long as the file has never been released.

      When a file is moved from the production folder structure to the concept folder structure, or form the concept folder structure to the production folder structure, the workflow and state needs to change. Currently this change is done by the engineer via change state.

       

      Is there a way for this to happen automatically upon moving the file?

        • Re: Can EPDM automatically change state upon file move?
          Joy Garon

          Hi Mark,

           

          Can you provide a screenshot of the workflow with the transitions back to the appropriate state? (maybe a cex file (export) is better).

          If it is proprietary, you can email it to me. I just want to understand the level of complexity before I suggest what I'm thinking...

           

          Joy

          • Re: Can EPDM automatically change state upon file move?
            Dennis Hvam

            Hi Mark,

             

            Are they a specific varible filled out when the files was created because if those files does have a variable you can  let that be a filter for the file to automatically move through another workflow:

            variable condition.png

             

            Or you could have a transistion that would go from one workflow to a specific state in another workflow and then move the files (I have not tested this but it should work)

            So they would still have to change state on the file and then move them. but it would solve your issue and you would write some variables in that transistion that this project from from XXXXX state XXX user did this transistion etc. just to keep track of things.

             

            /Dennis