JobScheduler Monitoring Interface - Send notifications for repeatedly failed job chain steps in JobScheduler release 1.10

Current Situation

• When an error reoccurrs in the same job node for which a notification has already been sent then this order state is considered being previously notified and no new notification will be sent.
• The JobScheduler Monitoring Interface can't differentiate if a job node has been restarted manually (e.g. by Resume Order) or if it has been automatically restarted by a setback setting.

Desired Behaviour

• In some cases, e.g. for long running orders, it is desirable that a reoccurring error results in repeated notifications.
• The following new functionality should be provided:
  1. Send notifications for all errors that occur, do not suppress errors for repeatedly failed executions.
     • Introduce a new configuration item for the JobChain element.
  2. Send notifications for errors that occur due to repeatedly failed executions if a configurable period of time is exceeded.
     • Introduce a new configuration item for the JobChain element.
• The solution should be provided as separate patches for previous JobScheduler versions (1.10.6, 1.10.7-1.10.11).

Maintainer Notes

• This feature will not be developed for branch 1.10 that comes to its end of life in August 2019.
• This feature is available with issue JITL-534 for branch 1.12