This may have been covered in a previous post, but there are too many to wade through when I search on "areavpath" so I apologize if this has been asked and answered before.
Is it allowable to have different tasks in a workflow reference areavpaths in different branches? The files will all be the same, just residing in different branches at different stages of the workflow. What I'm doing is a 3-tiered approach using branches and sub-branches to set up a development area, a QA area and a production area to store assets. This was presented to us by an Interwoven consultant, so it's all been blessed as a good approach. The development will start in a workarea within the lowest level sub-branch. When it's time for QA, the files are moved up one branch to a workarea in the QA branch and essentially locked while QA is performed. After QA approvel, the files are moved up one more branch to a workarea at the top level where the production version of the assets are kept. So as you can see, as the workflow progresses, people will be working on the same files in different branches. So my question is, can I reference different branchesfor areavpath in different tasks in the same workflow as long as the files are the same?
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
