Page History
...
- Error handling includes
- JS7 - How to detect job errors and warnings
- JS7 - How to handle job errors
- to decide if a job error can be handled automatically and
- an order can continue in the workflow,
- an order should leave the workflow.
- to decide if a job error requires user intervention,
- to decide if a job error can be handled automatically and
- JS7 - How to handle job warnings
- A JS7 - Notification can be created in case of job errors and warnings.
The following matrix shows possible combinations for the handling of job errors and warnings:
...
- The History outcome is not determined as the order remains in the workflow. The History outcome will be determined from later User Intervention.
- Notifications can optionally be sentare created.
- User Interventions include the following operations:
- Resume Order: The order will be continued at the same, at a previous or at a later workflow instruction.
- Child orders in Fork-Join and ForkList-Join instructions can be resumed within their branch.
- Suspend Order: The order will be suspended and will be resumed or cancelled later on.
- Cancel Order: The order will be cancelled and the History will indicate the failed outcome of order execution.
- Child orders in Fork-Join and ForkList-Join instructions leave their branch with a failed outcome that is adopted by the parent order.
- Resume Order: The order will be continued at the same, at a previous or at a later workflow instruction.
...
- The History outcome is not determined as the order continues in the workflow. The History outcome will be determined from later workflow instructions.
- Notifications can optionally be sentare created.
- User Intervention is not applicable.
...
- The History outcome is specified to be failed as a Fail instruction is used.
- Notifications can optionally be sentare created.
- User Intervention is not applicable.
...
- The History outcome is specified to be successful as a Try-Catch instruction is used to handle errors.
- Notifications can optionally be sentare created.
- User Intervention is not applicable.
...
- The History outcome is not determined as the order continues in the workflow. The History outcome will be determined from later workflow instructions.
- Notifications can optionally be sentare created.
- User Intervention is not applicable.
...
For earlier JS7 releases Notifications are not sent in case of job warnings.
Notification
For any above use case a JS7 - Notification is created.
- Notifications are visible from the JOC Cockpit user interface with the Monitor->Notifications view.
- Notifications can be configured to be forwarded
- by e-mail,
- by writing to a log file,
- by integration with a System Monitor or Message Queue (JMS).
The Monitor->Notifications view displays errors and warnings like this:
Jobs can be exempted from Notifications and they can modify notification settings:
- The Notifications tab in the properties editor for a job offers to overrule events when notifications are sent by mail:
- Mail on: Users can select one or more of the events ERROR, WARNING, SUCCESS.
- Mail To, Mail Cc, Mail Bcc: Users can specify recipients of e-mail notifications. An empty specification will prevent e-mail from being sent.
- The settings take precedence over general settings specified for JS7 - Notification.
Resources
- JS7 - How to detect job errors and warnings
- JS7 - How to handle job errors
- JS7 - How to handle job warnings
...
Overview
Content Tools