cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any way to maintain multiple 'instances' of a file?

boden
Champ in-the-making
Champ in-the-making
Let's say I've got a folder of files.  I want to make it so that regular users cannot modify the files in the folder directly, but instead have them somehow open the files for revision.

This is sorta doable using a simple workflow.  I can add a step "Open for Revision" which copies the file to a revision folder, and from there I can have whatever other steps in the revision / approval phase.  However, at the end, I'm just working with a copy.  This means that at the end of the approval chain, somebody is going to have to manually overwrite / update the original file. 

If instead of copying the file to a revision folder I had the workflow move the file, then a) the user would have to have permissions to move it, which means they could move it anywhere, right? and b) the file disappears from the original folder, which I don't want.

Unless I'm missing something, Alfresco isn't giving me any additional control here that a simple file share with permissions doesn't already offer.
3 REPLIES 3

daniel_gradecak
Confirmed Champ
Confirmed Champ
why not having different statuses around the file and not moving it really. You could move the file "physically" once it is archived or you do not need it anymore. Using a JBPM workflow (advanced workflow) and statuses could be a solution for you I guess.

boden
Champ in-the-making
Champ in-the-making
I think I asked my question poorly.

What I'm struggling with is merging changes.  Let's say a person opens a file that they can't write, and they make changes, then save it up to a "For Approval" space.  There doesn't seem to be a straight-forward way for the person doing the approving to update the original file without first downloading the new version, and the uploading it again using the "update" or "upload new version" feature on the original file.

It would be cool if a person could check out a file, creating a working copy somewhere that they can't check back in.  The working copy would go through an approval process at the end of which an authorized person could perform the check in.

daniel_gradecak
Confirmed Champ
Confirmed Champ
nothing forbids you to write your own actions (java, javascript …) and do that programatically. You should not think the way you see the JSF client …