Run Workflows on all Agents of a Subagent Cluster

Feature

• With JS-1986 a ForkList Instruction can be assigned a Subagent Selection. The Job Instructions inside the ForkList Instruction are forked for execution with all Subagents of the Subagent Selection.
• ForkList Instruction
  • JSON Schema Changes:
    • The ForkList Instruction is assigned a Subagent Selection

      {
        "TYPE": "ForkList",
        "agentName": "AGENT",
        "subagentClusterId": "SUBAGENT-SELECTION",
        "subagentClusterIdExpr": "$mySubagentSelection",
        "subagentIdVariable": "js7ForkListSubagentId",
        "workflow": {
          "instructions": [ ... ]
        }
      }
      

      • The agentPath element indicates the Agent ID.
      • The subagentClusterId element indicates the Subagent Cluster ID as fix string
      • The subagentClusterIdExpr element indicates the Subagent Cluster ID but the value comes from an Order variable (e.g. $mySubagentSelection).
      • The subagentIdVariable element indicates the name of the variable that can be used in subagentClusterIdExpr element  of the job inside the ForkList (default: js7ForkListSubagentId)
  • GUI Changes:
    • The ForkList optionally can be assigned a variable that holds the Subagent Selection ID.
• Job Instruction
  • JSON Schema Changes:
    • The Job Instruction is assigned an expression instead of a string to specify the Subagent Selection ID

      {
        "agentName": "AGENT",
        "executable": { ... }
        "subagentClusterIdExpr": "$mySubagentSelection",
      }
      

  • GUI Changes
    • Users can assign a Standalone Agent or Subagent Selection as usual from a list box entry.
    • Users can assign a variable that holds the Subagent Selection ID. This is performed by user input to a text box.