Workflows should be triggered by file orders if the workflow declares variables with default values

Current Situation

• Assume a workflow with a variable declaration like this.

    "orderPreparation": {
      "parameters": {
        "DRYRUN": {
          "type": "String",
          "default": "\"_\""
        }
      }
  

• Workflows carrying an orderPreparation element are not triggered by file orders.
• The above example workflow should be triggered by a file order as the declared variable is assigned a default value. The above example cannot work if the declared variable is not assigned a default value, see JS-2009.

Desired Behavior

• Workflows carrying an orderPreparation element should be triggered by file orders.
• If the orderPreparation element includes variables with default values only then the workflow should be triggered.
• If the orderPreparation element includes variables without default values then the workflow should be triggered and the file order should fail.

 Maintainer Note

• This issue is dismissed as there is good reason to stick to the existing functionality:
  • For workflows that do not use an orderPreparation element the situation is unchanged: the "file" order variable is automatically available.
  • For workflows that do use an orderPreparation element users have to add the "file" variable. Basically this means, if a declaration of variables is available then it has to be complete and has to include the "file" variable.

      "orderPreparation": {
        "parameters": {
          "DRYRUN": {
            "type": "String",
            "default": "\"_\""
          },
          "file": {
            "type": "String"
          }
        }