Posts

How do I know if Adobe Cloud Storage is enabled in my Workfront instance?

Image
How do I know if Adobe Cloud Storage is enabled in my Workfront instance? Go to Setup → System → Customer Info. Under Preferences, you can change the default to Adobe Cloud Storage when you are ready to move to Adobe Cloud Storage. Make sure testing is done in lower environments first before doing this in production. . We can also move to Cloud Storage portfolio by portfolio by using "Select Portfolios to Convert to Adobe Cloud Storage. Test Cases – Adobe Cloud Storage Migration To be tested once a customer moves to Adobe Cloud Storage: Project Conversion Test converting an existing (legacy) request to a new project on Cloud storage. Template-Based Project Creation Create a new project using an existing template and confirm it functions correctly on Cloud storage. Fusion Scenarios Validate existing Fusion scenarios continue to run without breaking. Specifically test document identifiers: confirm whether Document Version ID and Document ID references still resolve correctly — fla...
Post a Comment
Read more

Important points about Adobe's new Cloud storage in Workfront

  New version of Workfront — Rolls out on Adobe Cloud Storage, but it's opt-in and admin-controlled. Admins choose when to flip the switch, can pilot with specific groups (up to 10), and test in sandbox before going live. Adobe Cloud Storage replaces Workfront's own storage — Workfront, Frame, and Creative Cloud share one storage layer. This requires one Workfront instance paired with one Frame account in the same IMS org . Storage quota (GB per user) is pooled between the two. Frame.io replaces Workfront Proof as the review screen — Once cloud storage is on, Frame.io's viewer becomes the default review/markup tool, with better commenting/markup tools and a mobile app. The old Workfront Proof still works for legacy storage, with no set retirement date. Frame.io Enterprise adds creative work-in-progress features — internal-only commenting, secure external sharing with watermarks, and direct asset editing for creative teams, while Workfront still handles overall work m...
Post a Comment
Read more

Difference between UA and URA

UA = Unified Approval ("the lite version") This approval workflow can be used alone or with the legacy Proofing (ProofHQ) markup viewer/window Keeps the old review/markup screen (legacy Proofing/ProofHQ) — the actual screen people annotate documents on doesn't change. No new contract needed — Adobe just flips a switch on request. Works with legacy Workfront storage . AI Collaborator can be added into the approval template here too — so  a customer can get AI-assisted review even on the "lite" path, without needing to move to Frame.io. (Still needs its own prerequisites: Unified Approvals on + signed Gen AI agreement.) URA = Unified Review & Approval ("the full version," also called "V2") Everything UA has, plus it swaps in a brand-new review/markup screen powered by Frame.io instead of the old proofing viewer. Requires a new contract — A customer would need to sign the "V2 SKU" paperwork to unlock it. Which vi...
Post a Comment
Read more

How to add a new document version using Workfront Fusion

Image
  1. First add a Workfront Document Upload module and configure it as shown below
Post a Comment
Read more

Using if() for Field Fallback in Workfront Fusion

Image
  Logic: If the Event Coordinator field is populated, fetch that value. Otherwise, get the value from the Project Coordinator field. Formula: {{if(2.eventCoordinator; 2.eventCoordinator; 2.projectCoordinator)}} Explanation: This formula reads as: "If 2.eventCoordinator is populated, output 2.eventCoordinator ; otherwise, output 2.projectCoordinator ." Key point: You don't need to explicitly check whether 2.eventCoordinator is not empty — the if() function's truthy check already handles that. A populated field is treated as true by default, so the condition alone ( 2.eventCoordinator ) is sufficient without an additional !isEmpty() or similar check.
Post a Comment
Read more

Four Things You Can Automate with the Adobe Workfront Fusion v3 API

  Four Things You Can Automate with the Adobe Workfront Fusion v3 API If you're running Fusion at scale, you've probably hit at least one of these walls: you don't know which of your 200+ scenarios is still active, you blew your operations budget mid-month without a warning, promoting a scenario from dev to prod took half a day, or you woke up to a failure alert with no idea where to start. The Fusion v3 API is the answer to all four. Here's a practical breakdown of what you can automate — and how to get started in under 10 minutes. Before You Begin: Authentication Every call goes to https://fusion.adobe.io and requires four headers: Authorization: Bearer <IMS token> x-api-key: (from Adobe Developer Console) x-organization-id: (your target org) x-gw-region: (your gateway region) Set these up once in Postman as environment variables and every example in this post will work against your own tenant without modification. Setup in ...
Post a Comment
Read more

Workfront Calendar Visibility Issue

Workfront Calendar Visibility Issue Category Adobe Workfront – Calendar Management Affected Role Workfront Administrator Priority Medium   1. Issue Description   A Workfront administrator who originally created several calendars has left the organization and their user account is no longer active. Other administrators are unable to find some of those calendars in the calendar dropdown list. Symptom Calendars missing from the calendar dropdown for other administrators Trigger Original calendar owner's account was deactivated after leaving the organization Impact Calendars are inaccessible to the remaining team, disrupting scheduling and planning workflows   2. Root Cause   The original administrator did not grant other users or administrators access to the calendars they created. In Workfront, calenda...
Post a Comment
Read more