Posts

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 ...

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...

How to grant users access to Fusion via admin Console

  1.       Configuration in Admin Console: ·        Log in to the customer's Admin Console using this link: https://adminconsole.adobe.com/ ·        Navigate to Users and search for the user by their email address. ·        Click on the user. ·        Go to Products → click on the three dots (•••) → select Edit Products → click + → add the appropriate Fusion instance. ·        Grant the user access to product profile administration as well   2.       Configuration in Fusion: ·        Log in to the Fusion instance. ·        Navigate to Organization Overview → Users , where you will see the user created without an assigned Team . ·        Go to Team Overview, select the a...

How to Request a PDF Summary Using a Webhook

Image
Introduction When working with proof-based workflows, you often need to retrieve a PDF summary of a proof automatically. The Request PDF Summary module makes this easy. All it needs is a Proof ID and a Callback URL.   What You'll Need 1.   The Proof ID of the proof you want to summarize. 2.   A Callback URL — the destination URL where the PDF summary will be delivered. 3.   A custom webhook set up to receive the response.   What Is a Callback URL? The callback URL is simply the URL where the PDF summary of the proof will be sent once it's ready. Think of it as a return address you tell the system where to deliver the result, and it sends the summary there automatically.   Step 1 — Set Up Your Webhook Create a custom webhook to receive the PDF summary.  Step 2 — Configure the Module Open the Request PDF Summary module in your scenario. Enter the Proof ID and paste in your webhook's URL as the Callback URL.    Step 3 —...

Fixing “Read-Only” Issue in Workfront Proof (Peer Reviewer Can’t Comment)

The Issue A user was added as a peer reviewer in a Workfront Proof. However, when they opened the proof, they were unable to add comments — the proof appeared in read-only mode . Root Cause The issue was not related to permissions or roles. The real problem: The proof stage was locked. When a stage is locked in Proof HQ, reviewers in that stage cannot interact with the proof — including adding comments. The Fix Follow these simple steps to resolve the issue: Go to Proof HQ Open the proof in question Navigate to the Workflow section Locate the specific stage where the user is added Look for the 🔒 padlock icon Click on the padlock to unlock the stage Pro Tip Before troubleshooting user permissions: Always check if the workflow stage is locked This is a common reason for “read-only” behavior in proofs Final Outcome Once the stage is unlocked: The user regains full commenting access The proof behaves as expected for a peer reviewer

How to Convert Date & Time to Cvent Format in Workfront Fusion - 2025-06-07T06:25:00.000Z

Image
 Introduction When working with APIs or third-party systems in Workfront Fusion, you often need to send date and time in a specific format. If the format is wrong, your API call may fail. So let’s understand this in a very simple way What is Cvent Format? Cvent format looks like this: 2025-06-07T06:25:00.000Z This may look complicated, but it’s actually very simple when broken down. Understanding the Format YYYY-MM-DDTHH:mm:ss.SSSZ Each part means: YYYY → Year (e.g., 2025) MM → Month (01 = Jan, 02 = Feb, etc.) DD → Day (e.g., 07) T → Separator between date and time HH → Hour (24-hour format) mm → Minutes ss → Seconds SSS → Milliseconds Z → Time zone (UTC) Example 2025-06-07T06:25:00.000Z Means: Date → 7th June 2025 Time → 06:25 AM Timezone → UTC   How to Generate This in Workfront Fusion Use this simple expression: {{formatDate(now; "YYYY-MM-DDTHH:mm:ss.SSS[Z]")}}   Important Points Always use capital letters for format (...

Simple Fix for 400 Bad Request API Error (External Lookup)

Problem While selecting data from an external lookup field, an error occurred. API returned 400 (Bad Request) Cause The API URL was using an old version (v14.0) , which is no longer supported. Fix Just remove the version from the API URL. Before: /attask/api/v14.0/... After: /attask/api/... Result The API will use the latest version automatically Error gets resolved Takeaway If you see a 400 error, check if you're using an outdated API version.