-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Error trigger definitions are evaluated when externalTaskService.handleFailure and externalTaskService.complete are called.
Before evaluating error triggers, a context switch into a process application must be performed, so that beans, etc. can be resolved (=> look up how this was decided for conditional events in case of heterogeneous clusters and with respect to async continuations on tasks)
This is the controller panel for Smart Panels app
Extend External Task API with error event definitions
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Error trigger definitions are evaluated when externalTaskService.handleFailure and externalTaskService.complete are called.
Before evaluating error triggers, a context switch into a process application must be performed, so that beans, etc. can be resolved (=> look up how this was decided for conditional events in case of heterogeneous clusters and with respect to async continuations on tasks)