Adobe Workfront Fusion Developer Professional flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Operation

The billing and metering unit in Workfront Fusion; one bundle processed by one module counts as one operation, regardless of how much data the bundle carries.

Bundle

A single item of data passed between modules in a scenario. A module may emit zero, one, or many bundles per execution, and each is processed separately downstream.

Execution

One complete run of a scenario from trigger to final module. Each execution has its own history record, operation count, and per-module input and output bundles.

Scenario blueprint

The JSON definition of a scenario's modules, mappings, filters, and settings. Cloning copies the blueprint but not execution history or, unless reused, the webhook URL.

Router module

A branching module that sends a copy of each incoming bundle down every connected path. Filters on each path decide whether that path actually executes for the bundle.

Iterator module

A module that splits an array into separate bundles, one per element, so downstream modules process each element individually. The inverse of an array aggregator.

Array aggregator

A module that collects bundles from earlier modules and combines them into a single bundle containing an array, typically placed after a router or iterator.

Filter between modules

A condition evaluated per bundle; bundles that fail it are dropped and never reach the next module, though the producing module's operation is already counted.

Fallback route

A router path with no filter, or with a filter that catches everything the other paths rejected, used to handle bundles that no filtered branch accepted.

Connection

A stored set of credentials and scopes for an app. Multiple modules and scenarios can share one connection, so revoking it breaks all of them at once.

Search versus action module

Search modules return one bundle per match and can emit many bundles; action modules typically perform a write and return a single result bundle.

HTTP 429 response

The status returned when an app's rate limit is exceeded. Without retry or throttling, the module errors and the execution fails or follows its error handler.

Universal HTTP module

A connector that makes arbitrary HTTP requests without a dedicated app integration. Authentication is supplied by a selected connection or by headers you set.

Module interface change

When a module's output structure changes, downstream mappings referencing removed or renamed fields break until they are remapped to the new structure.

Mapping token syntax

Fields from earlier modules are referenced with double braces and a module number plus path, such as {{1.data.id}}, inserted by the mapping panel.

if() function

Returns one of two values based on a condition: if(condition; value_if_true; value_if_false). Arguments are separated by semicolons in Fusion expressions.

map() function

Extracts a specified field from every element of an array and returns the resulting array of those values, useful before joining or aggregating.

formatDate() function

Converts a date value into a string using a specified format and timezone. ISO 8601 is the safest interchange format between systems.

parseNumber() function

Converts a formatted string such as one containing commas or currency symbols into a numeric value so arithmetic functions can operate on it.

Break error handler

Attached to a module, it stops the execution when that module errors and marks the execution as failed, halting all downstream processing.

Resume error handler

Attached to a module, it supplies fallback output when the module errors and lets the execution continue with that substitute data.

Ignore error handler

Attached to a module, it lets the execution continue after an error, passing empty output downstream instead of halting or substituting custom values.

Incomplete executions

Failed executions whose state is preserved when the scenario allows storing them, so they can be inspected and resumed rather than rerun from scratch.

Idempotent create pattern

Checking whether a record already exists before creating it, so a duplicate webhook delivery or retry does not produce a second record.

Webhook trigger

A scenario trigger exposing a unique URL. The external app posts data to it, and the scenario runs immediately with that payload as the first bundle.

Polling trigger

A scheduled trigger that checks a source app at each interval and emits only items new since the last run, tracked by a stored watermark.

Webhook reuse versus clone

Reusing a webhook keeps the same URL for multiple scenarios; cloning issues a new URL, so callers still pointing at the old URL no longer reach the clone.

Run once

A manual execution that runs the scenario immediately regardless of its schedule, used to test a trigger and inspect real bundles before enabling it.

Team-based access

Scenarios belong to a team; team membership plus folder permissions determine who can view, edit, or run a scenario and its connections.

Least-privilege scopes

Requesting only the OAuth scopes a scenario actually needs, so a compromised or misconfigured connection cannot perform unnecessary writes.

Execution inspector

The per-execution view showing each module's input and output bundles, used to localize where a mapping is null or an API call fails.

HTTP status triage

Fast diagnosis of failing calls: 401/403 indicate connection or scope problems, 404 a wrong endpoint, 429 rate limits, and 5xx a remote app fault.