Split Workflow Not Triggering Condition

追蹤

Gwen Wilson

• 2021年03月05日 19:45

I have a workflow where I "made" a group of parallel tasks (I couldn't use the parallel tasks forms due to something downstream). In the current version, I have 4 approval forms. I need to add a 5th, but this one may be unassigned (and if so, then the approval task is skipped). So, I added a condition in front of it. However, when I publish and run this, the condition is not triggered at the same time as the other 4 task forms. They all are the same branch from the preceding step though.

Here's what it looks like (i highlighted the path to make it easier to see).

The condition isn't triggered

However, if I don't make the condition the first in this approval scenario and hook directly to the task, then it works fine.

Any thought on why the condition is not being triggered, and how to get this to work? I'm going to try sticking "fake" conditions in front of the original 4 and see if that will get the whole thing working. 

We are on version 7.0. This application was originally created in our previous version (6?) and migrated.

0

• 正式評論

  

  Sanjay

  • 2021年03月06日 00:12

  It looks like you have multiple incoming connections to the condition shape, so the condition shape is waiting for all incoming connections, hence it is not activated. Check WaitAllIncoming property of condition shape.

  評論操作 永久連結
• 

  Gwen Wilson

  • 2021年03月08日 16:52

  Thank you, Sanjay! I set the property to false and it works perfectly.

  0

  評論操作 永久連結

請登入寫評論。