Get started
Glossary
Definitions of the terms used across the Logic Fabric documentation, in alphabetical order.
Access control: The rules on a Logic API action that decide which callers may use it: an authorization policy and an optional precondition. See Access control.
Active version: The published version of a business process that new instances use. You change it with Activate or Publish & Activate.
After stage: The third stage of a recipe event. Its flows and business processes run after the record change is saved, right away or in the background (Async).
API Studio: The designer for Logic APIs, where you define modules, entities, actions, queries and access control, then publish versions. See API Studio.
Assignment: The part of a stage that decides who gets the work: a user, a team, each team member, or custom tasks.
Before stage: The second stage of a recipe event. Its flows and business processes run in the same transaction as the record change, before it is saved.
Business process: A long-running piece of work on a record, modelled in Process Orchestrator as stages, gateways and ends. See Process Orchestrator.
Completion criteria: A Yes/No condition over a stage’s tasks. When it becomes true, the stage completes and the process moves on.
Configuration value: One typed setting, such as a threshold or a URL, that logic reads with the Configuration Value function. See Configuration values.
Decision table: A logic block that maps combinations of conditions to outcomes, row by row. The first matching row wins. See Decision table.
Decision tree: A logic block that asks one question at a time until it reaches an outcome. See Decision tree.
Default path: The transition an exclusive or inclusive gateway takes when no other condition is true.
Draft: The editable version of a business process or Logic API. Publishing a draft creates a numbered version.
Edition: The variant of Logic Fabric for your platform: Logic Fabric for Dataverse or Logic Fabric for Dynamics 365 CE on-premises. See Editions.
End: A node in a business process that marks where a path finishes. The instance completes when no path is left open.
Escalation Monitor: The system record that watches due dates of stages that can escalate and starts each escalation shortly after the stage becomes overdue.
Escalation stage: A stage that a process moves to when its parent stage passes its due date without being completed. See Escalations.
Event: A named message with typed properties. A flow publishes it; event handlers react to it. See Events.
Event definition: The description of an event: its name and properties.
Event handler: A link between an event definition and a logic flow. When the event is published, the handler runs the flow, either immediately or in the background (Async).
Expose as Dataverse Action: A switch on logic blocks, logic flows and business processes that registers them as Dataverse custom actions. Once saved on, it stays on. On-premises label: Expose as Action.
Expose as MCP Tool: A switch on logic blocks, logic flows and business processes that makes them available as tools to AI agents through Logic Conductor. You can switch it on and off at any time.
Expression: A value or condition built in the expression editor from inputs, data, constants and functions. See Expression language.
Flow step: One action in a logic flow, such as Get Entity By Id, Condition or Create Email. See Flow steps.
Formula: A logic block that calculates one value, named result, from its inputs. See Formula.
Gateway: A node in a business process that splits or merges paths. Exclusive gateways take one path, parallel gateways take all paths, inclusive gateways take every path whose condition is true. See Gateways and ends.
Guard: The condition on a transition leaving a stage. When a stage completes, the first transition whose guard is true is taken.
Input: A value a logic block, flow or process receives when it runs. Must have a value marks it as required.
Localized resource: One piece of text with a translation per language available in the environment, read with the Localized Resource function. See Localized resources.
Logic Agents: The family of AI agents for Logic Fabric: Logic Assist, Logic Assurance, Logic Context, Logic Guard, Logic Insights and Logic Sentinel. See Logic Agents.
Logic API: The product that publishes governed, versioned REST APIs over Dataverse. See Logic API.
Logic Assist: The agent that builds and updates Logic Fabric artifacts from a plain-language description, with your approval. See Logic Assist.
Logic Assurance: The agent that generates and runs test suites for logic blocks and flows. See Logic Assurance.
Logic block: A reusable piece of logic that takes inputs and returns outputs without changing data: a formula, decision table, decision tree, validation or validation set. See Logic blocks.
Logic Composer: The product for building logic blocks, logic flows, recipes, events, schedules and integration settings. See Logic Composer.
Logic Conductor: The MCP server that turns the logic blocks, logic flows and business processes flagged Expose as MCP Tool into tools AI agents can run. See Logic Conductor.
Logic Context: The agent that generates a business requirements document from a project. See Logic Context.
Logic Fabric CLI: The command-line tool (with a PowerShell module) that exports, imports and promotes projects between environments. See Deploy & ALM.
Logic flow: A sequence of steps that runs top to bottom and can read and change data, branch, loop, call other logic and integrate with other systems. See Logic flows.
Logic Foundry: The MCP server that lets an AI assistant read, create and update Logic Fabric artifacts. See Logic Foundry.
Logic Guard: The agent that reviews a project against governance rules and suggests fixes. See Logic Guard.
Logic Insights: The agent that analyses business processes for health, performance and improvement opportunities. See Logic Insights.
Logic Sentinel: The read-only security-audit agent that maps who can reach which artifacts and data. See Logic Sentinel.
MCP (Model Context Protocol): The open standard that AI assistants and agents use to discover and call tools. Logic Foundry and Logic Conductor are MCP servers.
Output: A value a logic block, flow or process gives back when it finishes.
Precondition: Rules that decide who can run a logic block, flow or business process (Who can run / Who can start) and when (Run only when / Start only when). See Preconditions.
Process instance: One run of a business process on a record. It tracks the active stages, the path taken and the outcome. See Instances.
Process Orchestrator: The product for designing, running and monitoring business processes. See Process Orchestrator.
Project: The container for Logic Fabric artifacts, tied to one Dataverse solution and moved between environments as a unit. See Projects.
Publish: To turn a draft business process or Logic API into a numbered, read-only version.
Recipe: The link between logic and one Dataverse table. It runs validations, flows and business processes when records are created, updated or deleted. See Recipes.
Requirements-as-Code: The idea that business requirements are captured in a structured form precise enough to run, so the definition and the executable system are the same. See Why Logic Fabric.
Schedule: A timetable that runs a logic flow at a regular interval in a chosen time zone. See Schedules.
Service connection: The address, OpenAPI specification and credentials of an external REST API that flows call with Call Rest Api. See Service connections.
Stage: A step of work in a business process, with an owner, tasks, completion criteria and optional flows on entering and exiting. See Stages.
Template: A named set of properties defined on a block’s or flow’s Templates tab, used as a data shape.
Transition: A connection between two nodes of a business process. See Transitions.
Type: The kind of value an input, output, variable or expression holds, such as Text, Currency, Lookup or a list. See Types.
Validation: A logic block with one Yes/No rule that is Yes when the data is valid. See Validation.
Validation set: A logic block that runs several named rules and reports which ones failed, through the outputs isValid, failedValidation and failedValidations. See Validation set.
Validation stage: The first stage of a recipe event. Its validation and validation set blocks can stop the operation.