anchor.diff:  zero-padded values from the slot's scheduled time.
   
   `year`, `month`, `day`, `hour`, `minute`, and `second` will also be
  -set as Oozie properties, so they can be used in the workflow.xml.
  +set as Oozie properties, so they can be used in the Oozie workflow XML
  +file.
   
   Additionally, Celos will set the Oozie property `celosWorkflowName` to
   a string like "my-workflow@2015-09-12T20:00Z", useful for display.
  
positive.code: ===== Errors during job submission to Oozie do not bubble up into the UI
  
  If an error happens during job submission to Oozie (e.g. because the
  Oozie workflow directory is missing, or the workflow.xml contains a
  syntax error), the job will appear to remain stuck in the READY state,
  with no indication of error in the UI.  The log however, will contain
  the error.
  
  ==== The Celos name
  
  
negative.code: [source,javascript]
  ....
  celos.oozieExternalService({
      "oozie.wf.application.path": "/workflow-dir/workflow.xml",
      "prop1": "Hello. It is the year ${year}!",
      "prop2": "Just another property."
  });
  ....
  
  ===== Note
  
  `oozie.wf.application.path` is the only property required by Oozie.
  It points to a
  link:https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html[Oozie
  workflow XML file] within an Oozie workflow directory.  There can be
  multiple XML files within a single Oozie workflow directory.
  
  === Variables
  
  