Fusion Fundamentals and Architecture
Core Concepts
Adobe Workfront Fusion is a cloud-based automation platform that connects Workfront with other applications. It uses scenarios (automated workflows) composed of modules that perform actions. Modules are connected in a scenario to pass data along. Fusion operates on a trigger (the first module) that initiates the scenario, followed by action modules. Data flows as bundles (individual data items) between modules. Each module can output multiple bundles, which are processed sequentially or in parallel depending on settings.
Key Architectural Components
- Scenarios: The workflow container. Each scenario has a schedule or webhook trigger.
- Modules: The building blocks. Categories include triggers, actions, searches, and aggregators.
- Connections: Stored credentials for apps. They are reusable across scenarios.
- Data Stores: Persistent storage for data between scenario runs.
- Execution: Each run is an execution with a log of operations.
Traps in Questions
- Confusing bundles with items: A bundle is a single data record; multiple bundles are processed one by one.
- Misunderstanding trigger types: Polling triggers (e.g., "Watch Records") run on a schedule; instant triggers (webhooks) run immediately.
- Assuming modules always run in order: Some modules (like routers) can branch, and aggregators combine bundles.
Worked Example / Rule of Thumb
Rule of thumb: "Trigger first, then actions; bundles flow like items on a conveyor belt." For example, a scenario triggered by a new Workfront project (trigger) then creates a folder in Google Drive (action) and sends a Slack message (action). Each project is a bundle; if three projects arrive, the actions run three times.