NodeExecutionContext

NodeExecutionContext Shape

// BizFirst.Ai.ProcessEngine.Domain/Execution/NodeExecutionContext.cs
public class NodeExecutionContext
{
    // The per-element context — node definition, config, tenant ID
    public ProcessElementExecutionContext? ElementExecutionContext { get; set; }

    // Allows calling back into the engine (run sub-flows, signal events)
    public IOrchestrationProcessor? Processor { get; set; }

    // DataSections — shortcut to the operating context data
    public DataSections MyDataSections { get; set; }

    // Runtime metadata — timing, stage tracking, result pre-emption
    public NodeExecutionContextRuntimeInfo RuntimeInfo { get; set; }
}

ProcessElementExecutionContext — Key Fields

Access this via ctx.ElementExecutionContext:

// The most commonly used fields on ElementExecutionContext
ctx.ElementExecutionContext.TenantId        // int — tenant owning this execution
ctx.ElementExecutionContext.ExecutionId     // string — the workflow execution ID
ctx.ElementExecutionContext.NodeId          // string — this node's ID on the canvas
ctx.ElementExecutionContext.Definition      // ProcessElementDefinition — node definition
ctx.ElementExecutionContext.ResolvedConfig  // merged + expression-resolved config JSON
ctx.ElementExecutionContext.ExecutionMemory // access to upstream node outputs

Common Context Access Patterns

protected override async Task<NodeExecutionResult> ExecuteInternalAsync(
    NodeExecutionContext ctx, CancellationToken ct)
{
    var elCtx    = ctx.ElementExecutionContext!;

    // Tenant and execution identity
    var tenantId    = elCtx.TenantId;
    var executionId = elCtx.ExecutionId;

    // Already-populated settings (cast to your settings type)
    var s = (MyNodeSettings)settings!;

    // Access the orchestration processor (e.g. to trigger sub-flows)
    var processor = ctx.Processor;

    // Runtime perf — start time, elapsed, etc.
    var startedAt = ctx.RuntimeInfo.PerfMetrix.startedAt;

    // Data sections — variables, global data, etc.
    var variables = ctx.MyDataSections;

    // ... your logic ...
}

eNodeStage Enum

The runtime tracks which pipeline stage is currently executing via ctx.RuntimeInfo.StatusInfo.Stage. This is informational — you do not need to set it: