nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

submit in two branches within one workflow job

aliceharris · 2004-04-16T04:03:02+00:00

We have a workflow with these steps: * AuthorEdit in Branch_1 to create a file * Review_1 in Branch_1 * ExternalTask to:* copy the file (and its DCR) to Branch_2; * regenerate it to have Branch_2's appearance; * attach it to the workflow job (attached with a path relative to the job's workarea like this:…

aliceharris

We have a workflow with these steps:

AuthorEdit in Branch_1 to create a file
Review_1 in Branch_1
ExternalTask to:
- copy the file (and its DCR) to Branch_2;
- regenerate it to have Branch_2's appearance;
- attach it to the workflow job (attached with a path relative to the job's workarea like this: ../../../Branch_2/WORKAREA/etc)
Review_2 to review the Branch_2 file (the Branch_1 file is irrelevant for this reviewer)
Review_3 to review the Branch_1 and Branch_2 files to make sure they are suitable for submission
Submit the files in both branches

The two branches don't have the same directory structure and are for different websites.

All this works except that the Submit task can't submit the file in Branch_2 (the Branch_1 file submits correctly).

Is there a way to have a single Submit task that can submit files from more than one branch?

I'm aware that I could probably do something similar by replacing the ExternalTask and Review_2 with a nested workflow that creates, reviews and submits the Branch_2 file. However, we have a business reason for needing to have both the Branch_1 and Branch_2 files submitted at the same time, ideally immediately after Reviewer 3 has finished the review. I suppose we could have a second nested workflow just before the Submit task that does the Branch_2 submission, but I'm wondering if there's a neater way that doesn't involve two nested workflows?

Find more posts tagged with

Comments

Adam Stoller

submittasks will only submit files relative to their workarea root - and I don't think it groks ../ relative paths.

Instead, you could use an externaltask to create a file/comment list and run iwsubmit with that list to achieve what you want - but you'll also have to build in your own error handling and I'm not sure how easy it would be to generate a conflict task yourself, so you might have to have some convoluted code which, if it sees an error from iwsubmit transitions the job to a submittask and attempts the operation that way hoping to get it to trap and generate a conflict resolution task (but then you're back in the same boat you were in to begin with...)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

JonathonG

As an alternative to fish's suggestion, I believe you could just use 2 parallel submittasks, each with their areapath specified appropriately for the branch you want to submit from. The final review step would then transition to both of the submittasks, giving you the same-time submit that you are looking for. Caveat: I haven't ever done this, but I'm pretty sure it would work.

Jonathon
Independent Interwoven Contractor

james1

Yes, JonathonG is right. You need to have two parallel paths in your workflow.

You described your workflow in 6 steps. I will call these Tasks 1-6, plus a Task 7 for the endtask. The predecessors/activation for these tasks should be:

Task 1: N/A
Task 2: 1
Task 3: 2
Task 4: 3
Task 5: (needs to be split into two tasks, as a single usertask can be associated with exactly one workarea)
Task 5a: 4
Task 5b: 2
Task 6: (needs to be split into two tasks, as a single submittask can submit exactly one workarea)
Task 6a: 5a
Task 6b: 5b
Task 7: 6a AND 6b

You'll need to handle the rejection case yourself, not sure what is "correct" behavior for your situation.

-- James

--
James H Koh
Interwoven Engineering

Adam Stoller

I thought about the parallel task thing - and frankly I think it's a good way to go, but it seemed to me to be less 'atomic' than calling iwsubmit with the a full list of full vpaths and comments, which seemed to be a driving force in the request.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

aliceharris

[groan] That seems so obvious now! Smiley Happy

Thanks James for your detailed reply, and thanks Jonathon too! It's just what I was looking for.