Guides

Configuration

Suggest Edits

Configurations define the rules for how points are activated by Undirected Fill.

Example

Object

{
  "name": "default_undirected_configuration",
  "organization_id": "org_6595cb88cef61bf614830d14",
  "when": [
    {
      "task.intent": {
        "evaluate": true
      }
    }
  ],
  "flows": [
    {
      "action": "undirected_fill",
      "details": {
        "name": "default_undirected_configuration",
        "components": "enabled",
        "repeatable": true,
        "allow_additional_outputs": true,
        "on_multiple_points": "sequential",
        "on_no_points": "error",
        "max_points": 10,
        "partitions": [
          "expert-process"
        ]
      }
    },
    {
      "action": "run_intent",
      "details": {
        "name": "confirm_resolve_task",
        "components": "enabled",
        "repeatable": false,
        "required_outputs": [],
        "points": [
          "confirm_end_task"
        ],
        "allow_additional_outputs": false,
        "on_multiple_points": "sequential",
        "on_no_points": "error",
        "max_points": 10
      }
    }
  ],
  "tags": [
    "melodyarc-admin"
  ]
}

Highlighted Keys

  • when : An array of objects that define when the configuration point is triggered. This is a unique input used only for configuration points.

    E.g. "when": [ { "task.intent": { "evaluate": true } } ]

  • flows : An array of objects that define which fill methods to use, and the details of how they will be applied.
  • flows[X].action : The type of Fill to use. Can be undirected_fill, which selects undirected fill, or run_intent, which triggers Directed Fill.

🚧

Deprecating directed fill

run_intent and directed fill are legacy settings that will be deprecated.

  • partitions : An array of point partition names. If defined, only points within those partitions will be available for triggering.

Fill Triggers

Invoke points are triggered when the when criteria is met.

Updated 6 months ago

What’s Next