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; } } }

workflow successors

Ottawa_IWOV

Thought I would throw this out to the board:

Task C can be activated by Task A or Task B in once instance. But it would need both to be activated in another instance. How do I create the successorsets in this case?

Thanks,

Sorry if the above was confusing:

Task C could be activated by Task B, or activated by Task B AND Task A together. Make sense?

Edited by Ottawa_IWOV on 11/30/04 09:06 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

I don't believe there is a way to code what you are suggesting - can you provide a bit more of the use-case for this scenario?
The only way I can think of to do this would be to have a C1 and C2 task - where C1 can be activated by the 'or' clause and C2 requires the 'and' clause - but then you'd probably need an A1 & A2 and B1 & B2 tasks as well - thus significantly complicating the overall workflow design.

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

akshathp

is there a set criteria for when to activate Task C with only Task B and when to activate it with both Task A and B?

Akshat Pramod Sharma