https://answers.axonivy.com/tags/signals/?type=rss&user=vagabondquestions tagged <span class="tag">signals</span>enTue, 14 May 2019 10:30:00 -0400https://answers.axonivy.com/questions/3797/signal-wildcards-behave-in-an-unexpected-way<p>Hi Axon.ivy Team,</p> <p>I'm using Axon.ivy LTS 7.0.8 and I'm getting an issue related to <code>Signal</code>.</p> <p>I have 4 signal receivers:</p> <ol> <li> <p><code>one</code></p> </li> <li> <p><code>one:two</code></p> </li> <li> <p><code>one:two:three</code></p> </li> <li> <p><code>one:two:three:four</code></p> </li> </ol> <p>When I send the signal <code>one:two:three:four</code>, I expect that only the (4) receiver would be triggered. Unfortunately, I was surprised that <strong>all</strong> four of them were triggered.</p> <p><img alt="all four signal receivers are triggered" src="https://answers.axonivy.com/upfiles/image_(3).png"></p> <p>According to the official document, I would expect that only if I use the wildcard in the pattern of the Receiver, I will have the same behaviours (<code>one:*</code>, <code>one:two:*</code>, <code>one:two:three:*</code>) but in this case, the wildcard does not matter much here.</p> <p>Is it a bug or by design that the Signal Receivers behave like that?</p> <p>Thanks! Jack</p>vagabondTue, 14 May 2019 10:30:00 -0400https://answers.axonivy.com/questions/3797/signal-wildcards-behave-in-an-unexpected-waysignals