https://answers.axonivy.com/questions/3375/task-changes-priority-after-signalboundary<p>I have a UserTask that can optionally be cancelled by firing a Signal. When the Signal is actually received the Task seems to change its Priority from <code>HIGH</code> to <code>LOW</code>. Why does that happen? </p> <p><img alt="alt text" src="https://answers.axonivy.com/upfiles/userTaskPriorities.png"></p>enMon, 30 Jul 2018 09:13:12 -0400https://answers.axonivy.com/questions/3375/task-changes-priority-after-signalboundary/3377<p>SignalBoundaries on a UserTask are normally used to Expire a Task on an exceptional path. So it is a feature, that the state of this Task can be adjusted by configuring an expiry Priority.</p> <p>However if you don't like that behaviour you can change the priority back to its original state within the SignalBoundary event that handles the signal:</p> <pre><code>List&lt;ITask&gt; destroyed = signal.getDestroyedTasks(); ITask last = destroyed.get(destroyed.size()-1); ivy.task.setOriginalPriority(last.getOriginalPriority()); </code></pre> <p><img alt="alt text" src="https://answers.axonivy.com/upfiles/changeToPriorityBeforeSignalling.png"></p>Reguel WermelingerMon, 30 Jul 2018 09:13:12 -0400https://answers.axonivy.com/questions/3375/task-changes-priority-after-signalboundary/3377