Artifact Types
Logic Authoring can generate 13 artifact types across the platform's families. There is one type-specialist generator per family, each carrying the grammar and the real-world patterns for its type, so it produces metadata in the exact shape that type requires. Every type is generated, validated, and grounded through the same generate → validate → repair loop.
Logic Blocks
The atomic units of business logic. Five types:
| Type | What it is | What the generator produces |
|---|---|---|
| Formula | A single-output calculation or value derivation | The FoL expression, grounded to real fields and functions |
| Validation | A single business rule that accepts or rejects | The boolean condition, plus where its message is surfaced |
| Validation Set | A group of validations evaluated together | The member rules and the set's evaluation mode |
| Decision Table | Grid-based rule evaluation | The rows and columns, with the correct column count enforced by the verifiers |
| Decision Tree | Hierarchical branching conditions | The branch conditions and outcomes, including the default path |
See Logic Blocks for how these run.
Flows
| Type | What it is | What the generator produces |
|---|---|---|
| Logic Flow | A multi-step orchestration of actions | The action tree, with every invocation primed to the real input/output signature of the block, flow, or process it calls |
See Logic Flows.
Recipes
| Type | What it is | What the generator produces |
|---|---|---|
| Recipe | Entity-trigger wiring, runs logic on a Dataverse entity event | The recipe metadata bound to the real entity and its pre/post-operation events |
See Logic Recipe.
Business Processes
| Type | What it is | What the generator produces |
|---|---|---|
| Business Process | A multi-stage orchestrated process | The process definition, its stages and transitions, grounded to the real entity and referenced artifacts |
See Logic Process Orchestrator.
Events
| Type | What it is | What the generator produces |
|---|---|---|
| Event Definition | The declaration of an event and its payload | The definition and the payload shape |
| Event Handler | Binds an event definition to a logic flow | The handler wiring the real event definition to the real flow, sync or async |
See Event.
Scalars
Single-value configuration artifacts:
| Type | What it is | What the generator produces |
|---|---|---|
| Configuration | A typed, cacheable setting read at runtime | The value, its type, and its cache strategy |
| Localized Resource | A localizable string | The resource name and its per-language values |
| Schedule | A recurring trigger that runs a logic flow | The frequency and interval, bound to the real flow |
See Configuration, Localized Resource, and Schedule.
Single artifact, or a whole suite
Any of these can be authored on its own from a one-line description, or as part of a multi-artifact suite built from a single brief. In suite mode, the plan → reuse → build orchestrator works out the dependency order across types, so a brief like "validate the order, calculate its discount, and run it on order create" becomes a validation block, a formula block, and a recipe that triggers a flow using them, each built after the things it depends on already exist.
Editing existing artifacts
Beyond creating new artifacts, Logic Authoring makes targeted edits to any existing type. It fetches the current metadata, applies your described change, grounds and validates the result, and shows a before/after diff that you approve before it is written. See How It Works — Human-in-the-loop.