ForgeSchemaValidator Fails in Validating Schemas with Parallel Action or Subroutine elements about forge

[TravisOnGit]

Ack, that's odd. I'll get to this later in the week. Thanks for calling this out.

[nibalach]

I think the issue might be with the Properties element on the action node.

The schema validation somehow doesn’t seem to like single-line elements like Properties and Input on the action nodes.

Removing the Properties element seems to pass the schema validation:

{
    "RootTreeNodeKey": "Root",
    "Tree": {
        "Root": {
            "Type": "Action",
            "Actions": {
                "EvacuateAction_Evacuate": {
                    "Action": "EvacuateAction"
                },
                "NotifyCustomerAction_Evacuate": {
                    "Action": "NotifyCustomerAction"
                }
            }
        }
    }
}

Also observed it failing with a single-line Input property:

{
    "RootTreeNodeKey": "Root",
    "Tree": {
        "Root": {
            "Type": "Action",
            "Actions": {
                "EvacuateAction_Evacuate": {
                    "Action": "EvacuateAction"
                },
                "NotifyCustomerAction_Evacuate": {
                    "Action": "NotifyCustomerAction",
                    "Input": "C#|true"
                }
            }
        }
    }
}

But configuring the Input as a complex object with braces seems to pass the validation:

{
  "RootTreeNodeKey": "Root",
  "Tree": {
    "Root": {
      "Type": "Action",
      "Actions": {
        "EvacuateAction_Evacuate": {
          "Action": "EvacuateAction"
        },
        "NotifyCustomerAction_Evacuate": {
          "Action": "NotifyCustomerAction",
          "Input": {
            "myInput": "C#|true"
          }
        }
      }
    }
  }
}