How could we access the order object in job monitors?

• A job is executed as a taks and a task could run for many orders.
• Each order will be processed by the methods spooler_process_before(), spooler_process() (one ore more times) and spooler_process_after().
• The object spooler_task.order available in the method spooler_process_after() points to the order instance currently owned by the task.
  • The following examples are given in Javascript syntax, please consider the difference to ECMAScript syntax, see What are the differences between the SpiderMonkey, Rhino and Nashorn scripting engines?

 function spooler_process_after( spooler_process_result ) {
    spooler_log.info( "order id is " + spooler_task.order().id ) ;   // the order object is available
    return spooler_process_result;
 }

It is NOT available in spooler_task_after(), because no order is running for the current task any more.

 function spooler_task_after() {
    if ( spooler_task.order() == null ) {
      spooler_log.info( "spooler_task.order is null" );           // the order object is NOT available
    }
 }

It makes no difference if you run a shell job or an API job - this behaviour is the same.