You are viewing limited content. For full access, please sign in.

Question

Question

Help understanding Signal Catch/Throw

Forms
Updated November 17
asked on November 13

Hi all,

I'm trying to optimise a resubmission process, I've just been doing it through a workflow however, just wondering why this won't work.

The logic is when it hits the Signal Throw Event it sends a Signal back to the Catch Event which is tied to the approver task.

 

However when it hits the signal throw it just ends. Is the Signal Catch/Throw more for Parallel flows?

 

Thanks

 

1 0

Answer

SELECTED ANSWER
replied on November 13

Only active signal catch event can receive the signal.

With your flow, when the signal throw event is reached, the user task should already be completed.

The signal catch event would be completed when the user task it attached to is completed.

If you add a parallel gateway after the start event, and add a signal catch event on the other path, then it could keep active and receive the signal.

2 0

Replies

replied on November 15

It would be a lot simpler if you just used an exclusive gateway to loop back to the Approver task if resubmit was the action. I don't understand the need for a signal in this process.

0 0
replied on November 17

Thanks Rui, 

 

That makes sense.

0 0
replied on November 17

Thanks Kevin, 

 

Yes I have been using a loop I was just looking for a new way as sometimes the diagram can get quite messy and I was trying to have a singular loopback point.

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...