Files attached with Workflow.

Hi All,

I just want to know that files attached with workflow is the actual file in the workarea or they are from staging. Either it could just a pointer to the file present at the stagin area.

I have to deploy the file edited by editor to the preview server from there reviewer review the files and if accepted then deployed to production.

Please let me know, what I need to do in this case.
Don't mind but please explain the answer as I am very new to Interwoven and workflows... so I have very less understanding...

Thanks in advance.

Find more posts tagged with

Comments

Ambuj

Hi All,

I just want to know that files attached with workflow is the actual file in the workarea or they are from staging. Either it could just a pointer to the file present at the stagin area.

I have to deploy the file edited by editor to the preview server from there reviewer review the files and if accepted then deployed to production.

Please let me know, what I need to do in this case.
Don't mind but please explain the answer as I am very new to Interwoven and workflows... so I have very less understanding...

Thanks in advance.

Generally files attached to workflows are files from Workarea.

What do you mean by preview server? As I understand your requirement you can have a submit-approval workflow which can deploy files to production once it is approved by the approver (reviewer in your case). It seems to be a normal and simple approach.

If you have something specific then feel free to post your query. Smiley Happy

Migrateduser

yes , it seems simple but catch is when we submit the files, actually the files should move to different location where a reviewer can review the files(say moved to other workarea).

I just want to clearify here that the files attached to the workflow and the files moved from one location to other are same or not....

and now if the reviewer approve the files then should the files from the preview area to the production or the files attached with the workflow should move to the production..... (Here might be versions of both files are different) should I use locking method here...

Ambuj

yes , it seems simple but catch is when we submit the files, actually the files should move to different location where a reviewer can review the files(say moved to other workarea).

I just want to clearify here that the files attached to the workflow and the files moved from one location to other are same or not....

and now if the reviewer approve the files then should the files from the preview area to the production or the files attached with the workflow should move to the production..... (Here might be versions of both files are different) should I use locking method here...

I really don't understand as why you need to move your file to some other workarea. Reviewers can review it at same location.

Can you please explain as why you are going for such a complex and unusual approach?

Pawan

yes , it seems simple but catch is when we submit the files, actually the files should move to different location where a reviewer can review the files(say moved to other workarea).

I just want to clearify here that the files attached to the workflow and the files moved from one location to other are same or not....

and now if the reviewer approve the files then should the files from the preview area to the production or the files attached with the workflow should move to the production..... (Here might be versions of both files are different) should I use locking method here...

Do you intend to restrict the reviewer access to the other workarea only ?
In that case, you have to copy the file to the reviewer's workarea.
There is no need to test the existence of a file/dcr attached in the workflow, to the existence in the workarea, they are the same file.

If the reviewer approves the file, do you want to deploy it to the production server directly ?

kaalraa

yes , it seems simple but catch is when we submit the files, actually the files should move to different location where a reviewer can review the files(say moved to other workarea).

I just want to clearify here that the files attached to the workflow and the files moved from one location to other are same or not....

and now if the reviewer approve the files then should the files from the preview area to the production or the files attached with the workflow should move to the production..... (Here might be versions of both files are different) should I use locking method here...

Could you pls elaborate a bit about the branching structure you are using as your dev/test/stage/prod environments?

Adam Stoller

yes , it seems simple but catch is when we submit the files, actually the files should move to different location where a reviewer can review the files(say moved to other workarea).

I just want to clearify here that the files attached to the workflow and the files moved from one location to other are same or not....

and now if the reviewer approve the files then should the files from the preview area to the production or the files attached with the workflow should move to the production..... (Here might be versions of both files are different) should I use locking method here...

To be blunt - the files aren't attached to the workflow - references to files are attached to the workflow - and those references are evaluated in the context of the task's areavpath.

If you are copying files from one area to another as part of a task (updatetask, or externaltask or cgitask script) - then you need to [updatetask] provide both the source and target area vpaths, or [script] provide the same information to your script - usually basing one (if not both) on the task's areavpath.

The general reason for copying files to another workarea as you describe is if the reviewers have no access to the workarea in which the work was created, but do have access to another workarea where it can be reviewed.