Manifest Types

Empty Manifest

NodeExecutorManifest.Empty(ProcessElementTypeCode)

An empty manifest tells the platform: "This node exists and is registered, but has no field policy declarations. Apply defaults for all cross-cutting concerns."

When to use Empty

• The node has no fields requiring expression evaluation, data routing, HIL, or masking
• The node is a simple action — no human interaction, no sensitive data
• You are writing a new node and the full manifest is not yet designed (use Empty as a placeholder)

What the platform does with Empty

// StopWorkflow node — no fields, just halts execution
protected override NodeExecutorManifest? GetNodeExecutorManifest()
    => NodeExecutorManifest.Empty(ProcessElementTypeCode);

Full Manifest (From)

NodeExecutorManifest.From(
    ProcessElementTypeCode,
    fields: new[] { /* NodeFieldDescriptor[] */ },
    suspensionPolicy: null  // or: new SuspensionPolicy { ... }
)

A full manifest declares every field the node cares about and, optionally, a SuspensionPolicy if the node pauses and waits for human input.

When to use From

• The node has fields requiring evaluation, routing, HIL display, or security handling
• The node suspends and waits for human input (approval, form, chat)
• You need to control which fields a human reviewer sees and what they can do

Full example

protected override NodeExecutorManifest? GetNodeExecutorManifest()
    => NodeExecutorManifest.From(
        nodeTypeName: ProcessElementTypeCode,

        fields: new[]
        {
            new NodeFieldDescriptor
            {
                FieldId          = "to",
                Description      = "Recipient address",
                ExpressionPolicy = new ExpressionPolicy
                {
                    EvaluationStage = EvaluationStage.AtInputReady,
                    EvaluatorKind   = EvaluatorKind.Template
                },
                DataFlowPolicy = new DataFlowPolicy
                {
                    AcceptsUpstreamInput     = true,
                    ExcludeFromOutputMapping = true
                },
                HilPolicy = new HilPolicy
                {
                    SendToHil   = true,
                    DisplayMode = HilDisplayMode.ReadableContext,
                    InputMode   = HilInputMode.EditableOptional,
                    Label       = "To"
                },
                SecurityPolicy = new SecurityPolicy()
            }
            // ... more descriptors
        },

        suspensionPolicy: new SuspensionPolicy
        {
            TimeoutSeconds  = 86400,
            TimeoutPortKey  = "expired",
            TimeoutBehavior = TimeoutBehavior.AbsoluteDeadline
        }
        // or: suspensionPolicy: null
    );

Extension JSON (Database Overrides)

Extension JSON does not use "empty" vs "full" — it just lists the fields to add or override. The resolver merges JSON fields with the code manifest; only the properties present in JSON are overridden. Everything else keeps its code-defined values.

{
  "nodeTypeName": "email-smtp",
  "suspensionPolicy": null,
  "fields": [
    {
      "id": "body",
      "hilPolicy": {
        "sendToHil": true,
        "inputMode": "RequiredFromHuman",
        "label": "Email Body",
        "description": "Compliance requires you to confirm every email body."
      }
    }
  ]
}

Registration Flow