Completing Your Move to Unified Review & Approvals
In Part 3 of this 3-Part Unified Review & Approvals series, Mike Engel, Senior Product Manager, Adobe, walks through the remaining 5 key shifts for moving from legacy Proof-based review:
- Permissions live in Workfront Manage sharing in the project-sharing modal and it flows into Frame.io automatically, so don’t keep a separate permission set there. Manage and Contribute give edit and share access, View is comment-only, and outside reviewers can be invited by email without a Workfront license.
- Stricter naming rules Names must be unique within the portfolio or project, max 255 characters, and can’t contain characters like \ / : ; * ? " | < >. They also can’t end in a period or space. Workfront auto-fixes invalid characters (for example, a semicolon becomes a dash).
- Fusion scenarios must be rebuilt Scenarios for legacy Proof or document approvals don’t transfer because the data model, APIs, modules, and triggers differ. Teams moving early need to audit and update them, and an AI-assisted migration tool is targeted for next month.
- Workfront object behavior Legacy and Adobe Cloud Storage objects aren’t compatible. Portfolios can be converted, so existing projects stay as they are while new child objects use Adobe Cloud Storage, but legacy objects can’t be created under an Adobe Cloud Storage parent. Task and issue conversion works in one direction only and can’t be reversed. Legacy templates can create Adobe Cloud Storage projects, but they carry structure only, so documents and folder contents must be re-uploaded. Moving or copying documents between the two storage backends isn’t supported.
- Organizational change management Phased adoption over 4 to 12 months. ** Prepare in month one (confirm product access, assess impacts, set baselines like approval time and handoffs), test in month two with a group in a lower Workfront environment, then run a production pilot in month three with real projects and end-to-end testing with Frame.io. Months four through twelve cover phased expansion based on results and existing project lifecycles. Frame.io has no lower lanes, so end-to-end testing involving it must happen in production with an enabled group. Appoint a champion for each pilot team, make feedback visible, and track results against your baseline using Canvas dashboards.
This session included quick tips along with insight into the Product roadmap for what’s to come for Unified Review & Approvals.
Missed Part 1 or Part 2 of the Unified Review & Approvals series – no worries, access them on-demand:
New events are added every month, so make sure to check out the Experience League Events page for the latest sessions.
At a glance
Product: Workfront
Series: Workfront Workshops
Role: Admin,Developer,Leader,User