Update Workfront Fusion scenarios for unified review and approval
Workfront Fusion scenarios built on legacy Workfront Proofing don’t automatically work against Adobe enterprise storage projects. Proof-specific modules, webhooks, and API endpoints have direct equivalents in some cases and significant changes in others. This article helps you inventory affected scenarios, classify them, and decide on a remediation path before you bring teams that depend on those scenarios into your Adobe enterprise storage rollout.
Scenarios scoped to legacy Workfront projects continue to work as they do today. The remediation work described in this article applies to scenarios you intend to run against Adobe enterprise storage projects.
Fusion connectors with native support for unified review and approval are expected to be available in Q3 2026. Plan the rebuild now, but we recommend waiting for the new connectors before you build. Scenarios will be simpler and more reliable than what they replace.
Detailed automation guidance will be published alongside the Q3 2026 Fusion connector release. Use this article to inventory and classify scenarios now so you’re ready to act once that guidance is available.
For a high-level summary of what changes when your organization moves to Workfront on Adobe enterprise storage, see Move to Workfront on Adobe enterprise storage.
What changes for Fusion on Adobe enterprise storage projects
Existing Fusion scenarios built on Workfront Proof rely on proof-specific modules, webhook triggers, and API endpoints that aren’t part of the unified review and approval data model. The table below maps common scenario types to their expected impact and path forward:
Classify each scenario as Edit, Rebuild, or Retire
The work each scenario requires depends on what it does and what’s available in unified review and approval. Use the following classifications:
- Edit: The existing proof-related action has a direct equivalent in unified review and approval, and you can update the scenario to use the new action.
- Rebuild: The underlying steps have changed significantly, or new capabilities exist that the scenario should use, so the scenario needs to be rebuilt from scratch.
- Retire: Native unified review and approval functionality, such as multi-stage approval templates with deadline reminders, replaces what the scenario was built to do.
Review each scenario against your specific business logic to decide its classification.
Remediation approach
Use the following approach to plan and execute Fusion remediation:
- Inventory now. Pull a full list of active Fusion scenarios and tag every one that references proof creation, proof status, document approvals, or approval routing. Don’t wait until after Adobe enterprise storage is enabled.
- Classify each scenario as Edit, Rebuild, or Retire based on the criteria in the previous section.
- Pause proof-dependent scenarios before you bring teams that depend on them into your Adobe enterprise storage pilot. Running stale proof-based automations against the new model can produce silent failures or duplicate actions.
- Use approval templates to replace simple routing logic. Native multi-stage approval templates with deadline automation can handle many use cases that previously required Fusion. For more information, see Create an Approval Template for assets and documents.
- Wait for the Q3 2026 Fusion connector updates before rebuilding. The updated connectors expose modules built specifically for unified review and approval and make rebuilds significantly simpler and more reliable. We don’t recommend rebuilding against Workfront API version 22 beforehand. If you proceed for a time-critical scenario, plan to revisit that work once the new connectors are released.
- Test rebuilt scenarios end-to-end in a sandbox instance before enabling them in production. Pay particular attention to event subscription payloads — field names and schema differ from legacy proof events.