Hi,
I'm confronted with the following problem:
We have a structure based on multiple branches and multiple workareas, some people have access to one workarea in one branch but others have access to one (or again several) workarea(s) in several branches. For example, a content contributor would have acces to "content" branch, "daily" workarea. On the other hand, a developer would have access to "Navigation" branch and "Code" branch, and in one or several workareas of these branches.
Imagine that a content contributor enters a piece of content, and that for any reason (doesn't matter for the question itself) some code and/or navigation files has(ve) to be created, this means that the content contributor sends the file to the developer, who in time adds a file(s) from the corresponding workarea(s) [which could be any workarea in any branch] and then everything gets submitted to a common branch from where it is going to be deployed [Only generated code is submitted and users do not have access to the files in this workarea].
First and lasts point are a piece of cake, no problem there, the problem comes when I have to let the user select any file from any of the workareas he has access to. One would think of changing the "areavpath" of each individual task, but "areavpath" only allows for one workarea (and nothing but A workarea) to be entered, so it is not a solution. I thought about creating a "common" workarea where everybody would drop everything before attaching it to the workflow, but it would pose some security issues that people here won't allow to happen, so that is also out of the question.
Another solution would be to create an "intermmediate" task, that would allow the user to select which workarea he would like to work on, but this implies:
1-Changing the already instantiated job, how?? (so let's say task "ADD_FILES" has a new areavpath everytime it is called)
2-Only files from the same workarea would be allowed, so this would have to be a cyclic task (with succesors Add more files, continue to next task) in order to allow as much files to be added as needed.
Anyone has already ben confronted to a similar problem?? if so, which was your approach?? Just remember that changing the structure,asking why this auckward structure, or doing anything that would allow users to read/write non authorized files is simply not a solution here.
Thank you for taking your time reading this!!!!
Just Adding a thought that I have, making a CGI task where user would be able to pick up the files from no matter where. Cons, the workflow apparently needs all files to come from the same areavpath, is this correct ??? I've done some testings and everything that comes from the starting areavpath works but not the rest. Is my only possibility submitting everything to a common workarea and then re-submitting this everywhere it should be submitted??? I mean: Everytime a user adds a file(s) from a single workarea, everything goes to the common workarea and then when everything is approved, it goes to the definitive workarea(s).
Hmmmmm....
Edited by kiro on 03/31/03 07:11 AM (server time).
