elsa-core/doc/wiki
Sipke Schoorstra 52a7061f89
Merge release/3.8.0 into main
Brings the 3.8.0 release line into main, including the package-manifest
runtime-kind mechanism (src/PackageManifest.props + src/PackageManifestHints.cs)
that main did not have. All 72 manifest-producing packages now declare
compatibility.runtimeKinds = ["elsa.server"]; the two Bpmn modules added on
main pick this up automatically via their ShellFeatures directory.

Conflict resolutions:
- .specify/feature.json, CONTEXT.md, ROADMAP.md, build/_build.csproj: took
  main's, which is newer in every case. Verified byte-identical to main
  afterwards, so nothing from the release branch was dropped.
- NuGet.Config: union of package sources, minus valence-consolelogstream-feedz.
  main removed that feed deliberately in 7389e0a67 and now consumes
  ConsoleLogStreaming 1.1.0 from nuget.org.
- Elsa.sln: union of main's Bpmn projects and the release branch's
  ExternalAuthentication projects; the two sets are disjoint.

Reverted an unintended revert:

release/3.8.0 had lost commit 33181b2c9 ("test: cover Oracle bulk upsert SQL
generation") through an evil merge in c557c455a. That commit is present at the
merge base, so git resolved the release branch's older content as an
intentional change and would have silently undone it on main. It is three
coupled pieces:

  - test/unit/Elsa.Persistence.EFCore.UnitTests (deleted, plus its Elsa.sln
    project declaration and NestedProjects entry)
  - InternalsVisibleTo("Elsa.Persistence.EFCore.UnitTests")
  - the fix itself in BulkUpsertExtensions.GenerateOracleUpsert: internal
    visibility, ISqlGenerationHelper.DelimitIdentifier quoting, and explicit
    CAST(... AS NVARCHAR2(...)) on string columns

Dropping the third would have been an Oracle runtime regression: unquoted
identifiers lose case, and ODP.NET binds .NET strings as VARCHAR2 while Elsa's
Oracle migrations declare NVARCHAR2, causing a datatype mismatch. Merge base
and main are identical for that file and every hunk on the release side is a
revert plus cosmetics, so main's version was kept in full.

Accepted deliberate release-branch changes, verified as real refactors rather
than losses: AI EF Core migrations moved into the provider projects
(5c0d8b0f4), and AIPersistenceFeature.cs renamed to
EFCoreAIPersistenceShellFeatureBase.cs (ShellFeatures/ still present, so
manifest generation is unaffected).

Verified: dotnet build Elsa.sln succeeds with 0 errors and 2 pre-existing
NU1903 warnings; Elsa.Persistence.EFCore.UnitTests passes 1/1; all 72 emitted
manifests declare elsa.server and Elsa.Api.Common emits none.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 11:59:35 +02:00
..
activities-and-authoring.md Refresh codebase wiki (#7464) 2026-05-19 00:49:27 +02:00
architecture.md Add ingress rate limiting hooks (#7512) 2026-05-22 00:13:11 +02:00
build-run-operate.md Add read-only workflow runtime status permission 2026-06-16 23:27:59 +02:00
diagnostics-console-logs.md Enhance console logging with improved context and lifecycle (#7536) 2026-05-27 00:14:28 +02:00
diagnostics-structured-logs.md Refresh codebase wiki (#7464) 2026-05-19 00:49:27 +02:00
expressions-and-scripting.md [codex] Harden C# expression host-code execution (#7519) 2026-05-21 00:50:25 +02:00
extension-guide.md Add ingress rate limiting hooks (#7512) 2026-05-22 00:13:11 +02:00
health-checks.md Address health check review feedback 2026-05-21 02:13:19 +02:00
http-scheduling-resilience.md docs(wiki): point the scheduling link at StartupTasks 2026-08-12 00:02:13 +02:00
identity-tenancy-security.md Merge pull request #7534 from elsa-workflows/codex/update-wiki 2026-06-01 20:49:49 +02:00
module-system.md [codex] Add codebase wiki (#7453) 2026-05-16 11:54:27 +02:00
opentelemetry-workflows.md [codex] Fix console log metadata and type resolution (#7542) 2026-05-30 22:52:01 +02:00
output-converters.md Add output converter support at binding boundaries 2026-07-31 04:10:48 +02:00
persistence.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
README.md Add output converter support at binding boundaries 2026-07-31 04:10:48 +02:00
repository-map.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
specs-and-adrs.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
testing-guide.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
workflow-api.md Refresh codebase wiki 2026-05-23 14:19:02 +00:00
workflow-core.md Refactor: Overhauls workflow JSON type serialization (#7549) 2026-05-31 11:09:39 +02:00
workflow-management.md [codex] Add codebase wiki (#7453) 2026-05-16 11:54:27 +02:00
workflow-runtime.md Add read-only workflow runtime status permission 2026-06-16 23:27:59 +02:00

Elsa Core Wiki

This wiki is a repo-local, code-grounded map of Elsa Core. It is intended for contributors who need the same kind of fast orientation that a DeepWiki-style generated wiki gives: what the system is, where the important code lives, how the pieces connect, and how to safely extend or test them.

The source of truth is still the code, specs, ADRs, and tests. Each page links back to the relevant files so you can jump from explanation to implementation.

Start Here

Elsa Core is a modular .NET workflow engine. The main solution is Elsa.sln. Production code lives under src, tests under test, specifications under specs, and architecture decisions under doc/adr.

The shortest mental model:

  1. An application calls services.AddElsa(...).
  2. Elsa builds an IModule and configures feature objects.
  3. Features register services, activities, API endpoints, middleware, hosted services, and persistence stores.
  4. Workflow definitions are created by code, JSON, imported files, or providers.
  5. The runtime starts, resumes, dispatches, and persists workflow instances.
  6. APIs, SignalR hubs, HTTP endpoint activities, diagnostics, and persistence packages layer around that core.
flowchart LR
    App["Host app"] --> Module["Elsa module system"]
    Module --> Core["Workflow core"]
    Module --> Management["Workflow management"]
    Module --> Runtime["Workflow runtime"]
    Module --> Api["Workflow API"]
    Module --> Extensions["HTTP, Scheduling, Expressions, Identity, Tenants"]
    Management --> Persistence["Stores / EF Core providers"]
    Runtime --> Persistence
    Runtime --> Logs["Execution logs and diagnostics"]
    Api --> Studio["Elsa Studio / API clients"]

Page Map

Page Use it for
Repository Map Top-level folders, projects, and where to look first.
Architecture The main system layers and request/execution flow.
Module System How IModule, FeatureBase, feature dependencies, and shell features work.
Workflow Core Activities, execution contexts, pipelines, variables, bookmarks, graphs, and flowchart execution.
Workflow Management Workflow definitions, instances, import/export, materializers, validation, and activity descriptors.
Workflow Runtime Dispatch, triggers, bookmarks, queues, background activity scheduling, graceful shutdown, and recovery.
Workflow API FastEndpoints, route prefixing, API categories, SignalR, and client-facing contracts.
Activities And Authoring How workflows are authored in C#, JSON, ElsaScript, and host methods.
Output Converters How to register, configure, validate, discover, and operate bound-value converters.
Expressions And Scripting Expression evaluators and language feature packages.
HTTP, Scheduling, And Resilience Inbound HTTP workflows, outbound HTTP, scheduled triggers, and resilience strategies.
Persistence In-memory stores, EF Core stores, provider packages, migrations, and multi-provider rules.
Diagnostics Structured Logs ILogger capture, live feed, REST/SignalR surface, redaction, and SQLite persistence.
Diagnostics Console Logs Raw stdout/stderr capture, live feed, REST/SignalR surface, and redaction.
Health Checks Elsa runtime readiness probes, liveness/readiness mapping, and Kubernetes probe guidance.
Identity, Tenancy, And Security Users, applications, roles, API keys, tenant resolution, and authorization touch points.
Testing Guide Test project layout, fixture choices, and targeted commands.
Extension Guide How to add features, activities, expression providers, stores, endpoints, and ingress sources.
OpenTelemetry Workflow Instrumentation First-party workflow and activity traces and metrics emitted through System.Diagnostics.
Specs And ADRs How current specs and ADRs explain design intent.
Build, Run, And Operate Build commands, sample hosts, runtime knobs, Docker notes, and operational endpoints.

Source Landmarks

Contributor Workflow

Use targeted reads first, then targeted tests. For most changes, start with the relevant module page, inspect the linked feature class and contracts, add or update tests in the matching test/unit, test/integration, or test/component project, and run the narrowest dotnet test command that proves the behavior.

When changing public behavior, update the related README, spec quickstart, or wiki page in the same PR. This repository is strongly modular, so the best changes keep ownership boundaries clear.