Adobe Workfront Fusion Developer Professional key terms

A saved automated workflow in Workfront Fusion made of a trigger plus a chain of connected modules that run in sequence when the scenario is activated or manually started.

A single step inside a scenario that performs one action, such as retrieving records, transforming data, or creating an item in a connected application.

The unit of data passed between modules; each bundle is one item, such as one record or one file, and modules process bundles individually unless aggregated.

A single run of a scenario, whether triggered by schedule, webhook, or manually, with its own operation count, log, and success or failure outcome.

The billing and quota unit consumed by module runs; most actions cost one operation per bundle processed, and limits constrain how many a team can use.

The volume of payload data moved through a scenario, measured separately from operations and subject to its own plan-based allowance and overage rules.

The first module in a scenario that decides when and how the scenario starts, such as a webhook, a schedule, or a polling watch module for new records.

An HTTP endpoint generated by Fusion that receives incoming requests from an external system and immediately starts a scenario with the request payload as input.

A configurable webhook module where you define the expected payload structure, allowing Fusion to parse incoming JSON or form data into usable bundles.

The scenario setting that defines how often a scheduled scenario runs, from every fifteen minutes up to daily or on custom intervals, subject to plan limits.

A scenario that starts immediately when its webhook or mailhook receives data rather than waiting for the next scheduled polling interval.

The interface beside module fields that lists available output items from previous modules so you can drag them into fields instead of typing static values.

The act of linking an output value from one module to an input field in a later module so data flows dynamically through the scenario.

A formula written in Fusion's expression editor that combines functions, operators, and mapped values to compute a field value at runtime.

A built-in operation in the expression editor, such as text, math, date, or array functions, used to transform values inside a mapped field.

A function that returns a fallback value when the tested item is empty or missing, commonly used to prevent null errors in mapped fields.

A defined schema describing the fields and types of a payload, used by Fusion to parse, validate, and expose data for mapping in later modules.

A module that splits a single bundle containing an array into multiple separate bundles so downstream modules process each element individually.

A module that collects many bundles into one combined bundle, often producing an array or joined text for a single downstream action.

A module that splits the flow into multiple branches, sending each bundle down one or more routes based on filters attached to those routes.

A condition placed on a connection or route that decides whether a bundle continues; bundles failing the condition are dropped or routed elsewhere.

A special module attached to a module's error route that defines what happens when that module fails, such as retrying, ignoring, or running a fallback path.

A setting that tells Fusion how to handle a module failure, including options to resume, ignore, break, roll back, or commit the scenario's progress.

A directive that stops the scenario and reverses changes made during the current execution where the connected app supports it, preventing partial data writes.

A directive that finalizes and keeps all changes made so far in the execution, then stops the scenario without processing further modules.

A directive that stores the failed bundle and incomplete execution state so a later run can resume processing from that point.

A stored execution that stopped before finishing, often due to an error or break directive, which can be reviewed and resumed or deleted from the queue.

A scenario setting that forces executions to run one at a time in order rather than in parallel, which helps prevent race conditions on shared records.

A design property where running the same operation multiple times produces the same result, important for safely retrying failed or duplicate executions.

A stored credential linking Fusion to an external application, created through authentication and reusable across modules and scenarios in the same team.

An authorization protocol where the user grants Fusion scoped access to an app without sharing a password, producing refreshable access tokens.

A secret token passed with requests to authenticate to an application, stored in a Fusion connection rather than hardcoded into module fields.

The organizational container in Fusion that owns scenarios, connections, and usage; members share resources and permissions within their team.

A permission level assigned to a team member, such as admin, member, or restricted user, controlling what scenarios and settings they can view or change.

The top-level account container that holds multiple teams, manages overall licensing and operation allowances, and sets governance across the account.

The record of saved scenario revisions that lets you review prior configurations and restore an earlier version if a change breaks the workflow.

A JSON export of a scenario's modules, mappings, and settings that can be imported into another team or environment to recreate the workflow.

A copy of an existing scenario created for testing or reuse, which can be modified without affecting the original live workflow.

The detailed per-execution record showing each module's input, output, operations used, and errors, used to diagnose why a run failed.

The practice of inspecting execution logs, testing individual modules, and running scenarios with limited data to locate and fix faults.