Attaching a file using command line in the workflow

Hi,

I have a workflow model which has one DCR attached to the initiated job, in one of the external task I need to attach one more DCR with the same name but in different branch path. This DCR would be a translated DCR of the original DCR.

original DCR sample path: /default/main/samplebranch.com/WORKAREA/work/templatedata/hotel/hotel_info/dcrname.dcr

translated DCR sample path to be attached to the job using CLT
/default/main/samplebranch.uk/WORKAREA/work/templatedata/hotel/hotel_info/dcrname.dcr

Please help me understand if this is possible. I did try to use a CLT

iwaddtaskfile -s "server ip" "taskid" templatedata/hotel/hotel_info/dcrname.dcr "Attached to test"

while being in /default/main/samplebranch.uk/WORKAREA/work directory. But I get an error ERROR:00017: Item already exists

I read that iwaddtaskfile takes the file path relative to the areavpath so is there no way a workflow can have files from different branches and workareas?

Please help, this is urgent.

Find more posts tagged with

Comments

Adam Stoller

Hi,

I have a workflow model which has one DCR attached to the initiated job, in one of the external task I need to attach one more DCR with the same name but in different branch path. This DCR would be a translated DCR of the original DCR.

original DCR sample path: /default/main/samplebranch.com/WORKAREA/work/templatedata/hotel/hotel_info/dcrname.dcr

translated DCR sample path to be attached to the job using CLT
/default/main/samplebranch.uk/WORKAREA/work/templatedata/hotel/hotel_info/dcrname.dcr

Please help me understand if this is possible. I did try to use a CLT

iwaddtaskfile -s "server ip" "taskid" templatedata/hotel/hotel_info/dcrname.dcr "Attached to test"

while being in /default/main/samplebranch.uk/WORKAREA/work directory. But I get an error ERROR:00017: Item already exists

I read that iwaddtaskfile takes the file path relative to the areavpath so is there no way a workflow can have files from different branches and workareas?

Please help, this is urgent.

A task in a workflow is associated with a specific area (usually workarea) on a specific branch.
Files associated with a task are all relative to the area associated with the task (and I don't believe that ../ relative paths will work - at least not into other TS areas)

You either need to use a split-path, sibling, or nested workflow.
Split-path is rather confusing and often difficult to manage (it's basically like a concurrent review process - but the split threads can never come back together again because of the differences in area paths)
Sibling is basically an externaltask used to fire off another instance of the workflow with the other file - there's no "relationship" between the workflows (except that which you might create and manage yourself)
Nested workflows are documented in the manuals and in various posts in the forums - they have their pros and cons too.

sasikumarg

Hi Ghoti,

cant we invoke a cgi say like cross branch browser cgi to browse the files from multiple workareas and attach the files to the task? will this work? Can you please suggest me some other work around apart from nested workflow ?

Hi dolly,

Ghoti please correct me if I am wrong, you can copy the translated DCR to the current workarea during instantiation or before adding of the files thru external task and proceed further with your process,once done you can delete the file from current workarea.

I guess this is possible..will this possible ghoti??

~S.

ISCBorisB

Hi Ghoti,

cant we invoke a cgi say like cross branch browser cgi to browse the files from multiple workareas and attach the files to the task? will this work? Can you please suggest me some other work around apart from nested workflow ?

Hi dolly,

Ghoti please correct me if I am wrong, you can copy the translated DCR to the current workarea during instantiation or before adding of the files thru external task and proceed further with your process,once done you can delete the file from current workarea.

I guess this is possible..will this possible ghoti??

~S.

You can of course browse anywhere, using CGI or External Tasks GUI and code.

However, you won't be able to attach Files belonging to the different Areas to the same Task. Ghoti already explained that
"Files associated with a task are all relative to the area associated with the task". Task Object has only one 'areavpath'
Attribute so only Files from that single Area can be attached. You can perhaps design a Workflow that manipulates Tasks with
various Areas, not that it's a stellar idea IMO.