Jobs

A job is a list of tasks created from a key pair set of variables in a template, and converted into a list of tasks via a plugin

Job States

All running jobs can be found in the running directory, all failed jobs can be found in the failed directory and so on. Each job is responsible for moving itself from the start state.

Each task in the job file is checked for a return code and all the tasks will either complete, in which case, the file link is moved into the completed directory, or a specific task in the job will fail and the job is moved to the failed directory.

States

STATE		Process control into state	Process control out of state
Completed	JOB				fn_HouseKeeping
Deleted		fn_HouseKeeping			fn_HouseKeeping
Failed		JOB, Rules engine		User
Fixing		User				User
New		User, external process		User
Pending		Rules Engine			fn_Dispatcher
Queued		User, fn_ProcessRequest		fn_Dispatcher
Running		JOB				JOB
Started		fn_Dispatcher			JOB
Superseded	fn_ProcessRequest		User

The Task displays are handled at job run time. Each Task state transition is added to the footer of the job

Example:

AUDIT:T:0:R
AUDIT:T:0:C
AUDIT:T:1:R
AUDIT:T:1:C
AUDIT:T:2:R
AUDIT:T:2:C
AUDIT:T:3:R
AUDIT:T:3:C
AUDIT:T:4:R
AUDIT:T:4:C
AUDIT:T:5:R
AUDIT:T:5:M

State

Job State          Value     Display
Running            R           >>>
Failed             F         [failed]
Manual             M         [manual]
Skipped            S         [ skip ]
Complete           C         [ done ]
Tried and Failed   T         [ TaF ]