Job Events

Job events are available as a setting (see Job Events tab) on most modules.

They are used to generate an event when a job reaches a predefined condition. A job event is effectively a new type of destination activated at a later time if certain criteria are met.

It is possible to have Lasernet activate when a job or job group completes, succeeds, or fails.

Success

Once Lasernet has finished processing the job, the event will only occur if the job was successful.

Failure

Once Lasernet has finished processing the job, the event will only occur if the job has failed.

Combined

Once Lasernet has finished processing the job, the event will only occur if the job is combined.

Paused

Once Lasernet has finished processing the job, the event will only occur if the job is paused

Scheduled

Once Lasernet has finished processing the job, the event will only occur if the job is scheduled.

Levels

Jobs flow through Lasernet in a tree-like fashion. Each time a job is passed, a clone or branch is created.

The level of the tree where the job event is set up determines the outcome. Only jobs below this level are considered when determining if a job group is completed, successful or failed.

JobData

Generally, JobData is not needed for the event and as such it is not stored to disk or used (by default).

JobEvent

A JobEvent is defined by the following properties:

It is possible to have JobInfo criteria for determining if an event should occur or not.

A list of additional JobInfos to store in the XML Job tree is available.

Example

1. An input job is passed through an engine and out through an output module. A Job Event is defined for the input job.

When the event occurs, the Job is passed to the Job Event destination alongside the XML tree, which then contains info about these jobs:

• Input Job

• Engine Job

• Output Job

2. Instead of placing the Job Event on the input Job, it is put on the output Job. Now the tree will only contain info about the output Job and not the engine Job nor the input Job.