The FileOrderVariablesJob adds order variables from an incoming file

Desired Behavior

• File orders should carry order variables to resolve variables that are declared in a workflow orderPreparation element with or without default values.
• Variables for file orders can be used from incoming files:
  • The incoming file can hold pairs of names and values similar to the temporary file available from the $JS7_RETURN_VALUES environment variable for return values of shell jobs: <name>=<value>.
    • pairs of names/values are separated from each other by EOL which can be CR, CRLF or LF.
    • The <value> can include the = character.
    • The <value> can include any Unicode characters.
  • A new JITL Job FileOrderVariablesJob implements the functionality:
    • If the related incoming file holds pairs of names and values for variables then they are added to the order as return values from the  JITL job.
    • If the related incoming file is empty then no return values are created and no error occurs.
    • If the related incoming file includes content that does not match name/value pairs then an error is raised.
  • The JITL job does not use any arguments to specify its processing mode. Instead, users can add any arguments to this job that are expected to match the name of a name/value pair in the incoming file:
    • job arguments that are not assigned a value are considered optional for the incoming file. Respective return values are created only if the incoming file provides the variable. This includes that the incoming file specifies an empty value for the variable.
    • job arguments that are assigned a value are considered optional.
      • If the incoming file does not provide the variable then a return value with the JITL Job's default value is created.
      • If the incoming file provides a variable - optionally with an empty value - then a return value with the value from the incoming file is created.
  • For pairs of names/values for which no job arguments are specified the JITL Job will raise an error.