Can a Workflow submit files from different Branches?

Can a Workflow submit files from different Branches?

Example:
We have branch ZZZ as a top branch which contains sub-branches 1,2 and 3. The workflow we are considering will create files in branches 1,2 and 3. Users will update the files in all 3 branches and upon completion of this the workflow will submit the content of all 3 branches at once.

Find more posts tagged with

Comments

ISCBorisB

Can a Workflow submit files from different Branches?

Example:
We have branch ZZZ as a top branch which contains sub-branches 1,2 and 3. The workflow we are considering will create files in branches 1,2 and 3. Users will update the files in all 3 branches and upon completion of this the workflow will submit the content of all 3 branches at once.

It is possible within certain limitations. Most important of these is the fact that you can not attach Files from
multiple Areas to the same Workflow. What it means is that you may have to code some WF functionality that is
normally provided by WF Engine (like lock/unlock etc...) For the same reason 'submittask' can not be used, not directly
anyway. You'll have to use iwsubmit commands in the External Task or perhaps start individual (sub)workflows with proper
'iw_workarea' wft Tags.

Also, you'd have to carefully consider where to initiate this workflow from. If it is some Workarea of one of the branches,
you would be able to attach Files from this WA and use this set as *model* for the rest. Note that to allow initiation
from read-only Areas like STAGING you'd have to explicitly set all your tasks read-only.

cesarecastro

So, I take from your response that it is possible for a single workflow to initiate tasks across distinct branches. Please let me know if my assumption is correct.

I am also considering, as you mentioned, having nested Work flows to be initiated from branch 1 and kicking of child work flows in branches 2 and 3. I am just trying to figure out the best practice and design.

Adam Stoller

It is possible within certain limitations. Most important of these is the fact that you can not attach Files from
multiple Areas to the same Workflow. [...]

I believe that limitation is for tasks not workflows
The task is associated with a specific areavapth
You can have multiple tasks, with each one representative of a different areavpath - e.g.:

                       /-(usertask[b1/wa1])->...
(externaltask[start])-+--(usertask[b1/wa2])->...
                       \-(usertask[b2/wa1])->...

What it becomes difficult to do is to ever bring the separate process flows together again, because that would indicate a merging of the lists of files associated with each task which then might not make sense given that you would only have one, instead of three (in this example) different areas to associated with those file paths.
The lead-off externaltask shown above, could be an updatetask (simple fork), or it could be just what it shows, with code internally doing iwupdate, or doing something more complex.

Another alternative is to fork off the work in different areas to different [sub-]workflows, so that each workflow is consistent within itself, and only if/when they come back together to transition the parent workflow do you need to think about if/how to bring the file lists together.

Adam Stoller

So, I take from your response that it is possible for a single workflow to initiate tasks across distinct branches. Please let me know if my assumption is correct.

I am also considering, as you mentioned, having nested Work flows to be initiated from branch 1 and kicking of child work flows in branches 2 and 3. I am just trying to figure out the best practice and design.

I think "best practice" is to avoid having to do this unless absolutely necessary, and if absolutely necessary - to have complete details of the rationale and requirements before trying to figure out the best design for it.