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

Question

Question

Signal Catch Event in Laserfiche is blocking the process from advancing

asked on December 9, 2020

Hello everyone! 

I am using Laserfiche Forms Professional Version 10.3.1.553 at a customer and i come to you for some guidance or maybe some clarifications about the signal catch event activity behavior.

So in the attached image, you will see a part of the process where i'm facing the issue. In this image the process goes as follows:

  1. The #1 signal throw event throws a signal  to the #1 signal catch event.
  2. Then depending on a certain condition of a value already filled by the user in the below parallel path, either #2 or #3 signal is thrown.
  3.  When #2 or #3 signal is thrown, of course the signal catch events in the parallel path will listen and catch it.

 

The expected behavior is to stop the process from advancing until the signal catch event activity is reached an and knowing that its respective was already caught, the process will then advance. 

The problem I'm facing is that, the signal catch #2 or #3 ( assuming its corresponding signal was thrown before the process them ) is blocking the process from advancing to the next task. 

When i check my monitor tab, i can clearly see that the task is stuck on that step as shown below. 

Now my question is, does the signal catch event work even if the signals were thrown before the process reaches the catch event ? or should i design the diagram in a way that, any signal throw event, must be thrown only after the process reaches a catch event ?

Your input is highly appreciated!

Joseph

0 0

Answer

SELECTED ANSWER
replied on December 9, 2020

The signal catch event can only catch the signal throw after it is reached. You can click the "Manual Trigger" action from the instances history as workaround if the signal is thrown before reached the signal catch event.

0 0
replied on December 9, 2020

Hello Xiuhong,

Thank you for your answer. 

I've been telling the customer to manually trigger it as you mentioned for a while now but of course this is not the perfect application for an automated process architecture. 

Appreciate your clarification! I guess I'm gonna have to change this part of the implementation then enlightened

Regards.

0 0

Replies

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

Sign in to reply to this post.