How to Create an Advanced Proof Using Workfront Fusion

 In this video, we walk through how to create an Advanced Proof in Adobe Workfront using Workfront Fusion. An advanced proof is simply a proof that has an automated approval workflow attached to it (also known as a workflow template).


🔍 What You'll Learn in This Video

https://www.youtube.com/watch?v=5UfBUotJONk

1️⃣ Create the Advanced Proof Manually


Open the document


Choose Create Proof → Advanced


Select Automated Workflow


Pick your workflow template


Review the stages


Trigger the proof creation


2️⃣ Capture the Network Traffic


Open DevTools (F12)


Switch to the Network tab


Trigger the proof creation manually


Find the API call behind the scenes


Locate the advancedProofOptions JSON


Copy the exact JSON payload into a Notepad


3️⃣ Configure Workfront Fusion


Add a Workfront (MISC action) module


Select the correct connection


Choose Record Type: Document


Select Action: Create Proof


Retrieve:


Document ID (first GUID in URL)


Document Version ID (second GUID in URL)


Paste the advancedProofOptions JSON captured earlier


Save and execute the module


4️⃣ Test & Validate


Run the module


Refresh the document


Confirm the proof has been generated


Open the proof and verify:


Stage 1


Stage 2


Automated workflow setup


🎉 Result


You’ll see how Fusion successfully creates an automated, multi-stage advanced proof—just like the UI does—using the captured API payload.


👍 Don’t Forget


If this tutorial helped you:


Like the video


Share it with your team


Subscribe for more Workfront & Fusion automation tutorials


#Workfront #WorkfrontFusion #AdvancedProof #WorkfrontProof #AdobeWorkfront #Automation #WorkflowAutomation #ProjectManagement #WorkfrontTutorial #FusionTutorial #APIIntegration #ProofWorkflow #DigitalProofing #WorkfrontTips #automatedworkflow 

The JSON message inserted under advancedProofingOptions is given below.


{

  "parentFileToken": null,

  "customfields": [],

  "hasSelfClose": false,

  "isLoginRequired": false,

  "hasElectronicSignatures": false,

  "canDownload": true,

  "hasPublicSharing": true,

  "hasSubscription": false,

  "stages": [

    {

      "name": "Stage 1",

      "position": 1,

      "parentPosition": null,

      "deadlineCalculateOn": null,

      "deadlineDate": null,

      "deadlineBusinessDays": null,

      "deadlineTime": null,

      "activateOn": 1,

      "activateOnDecision": null,

      "activateOnDate": null,

      "lockOn": 1,

      "isPrivate": false,

      "isOneApproval": true,

      "isMandatory": false,

      "recipients": [

        {

          "role": 3,

          "email": "xyz@xyz.com",

          "notifications": 3,

          "isPrimaryDecisionMaker": false,

          "permissions": {

            "resolveCommentsAndActions": true,

            "shareProof": true

          }

        }

      ]

    },

    {

      "name": "Stage 2",

      "position": 2,

      "parentPosition": null,

      "deadlineCalculateOn": null,

      "deadlineDate": null,

      "deadlineBusinessDays": null,

      "deadlineTime": null,

      "activateOn": 1,

      "activateOnDecision": null,

      "activateOnDate": null,

      "lockOn": 1,

      "isPrivate": false,

      "isOneApproval": false,

      "isMandatory": false,

      "recipients": [

        {

          "role": 5,

          "email": "abc@gmail.com",

          "notifications": 3,

          "isPrimaryDecisionMaker": false,

          "permissions": {

            "resolveCommentsAndActions": false,

            "shareProof": false

          }

        }

      ]

    }

  ],

  "isOneApproval": false,

  "isAutomatedWorkflow": true,

  "stageBasedVisibility": 0,

  "ownerUserToken": "Insert_Owner_Tokem",

  "templates": [

    {

      "token": "Insert_Token"

    }

  ],

  "hasCustomMessage": false,

  "hasMessage": true,

  "subject": "",

  "message": ""

}

Comments

Post a Comment

Popular posts from this blog

Error: Number of included segments do not match

Introduction In this blog, we tackle a crucial issue encountered during the reprocessing of an X12 EDI message. We will get into the root cause of the problem and provide you with a solution to overcome it. Error: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:       Error encountered during parsing. The X12 transaction set with id '103465910' contained in functional group with id '02', in interchange with id '000000009', with sender id '4532345856     ', receiver id '8038025150     ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Number of included segments do not match . The sequence number of the suspended message is 1.  Root Cause: The issue stems from a mismatch in the number of se...
Read more

REST API Calls with Query Parameters in BizTalk: A Step-by-Step Guide

Image
 Introduction In this blog, I will provide a comprehensive guide on how to call a REST API that requires query parameters. We'll walk through the necessary steps to set up the environment and make successful API calls. Solution High Level Steps 1. API Overview: We will be using an open API for demonstration purposes. The API endpoint we'll be working with is: https://randomuser.me/api/?results=1 2. Schema Creation: Create a schema named "SourceA" that matches the structure of the messages you'll be dropping in the receive location. To create a JSON response schema, follow these steps: capture the JSON response by running a test in Postman, and then utilize a JSON schema generator to create the desired JSON schema. 3. Field Promotion: In the SourceA schema, promote the field called "results." This field will serve as the variable for the query parameter. 4. Receive JSON Pipeline: Develop a receive JSON pipeline that can receive JSON messages and convert t...
Read more

Updating BizTalk SSO DB using BTDF and a simple BTDF deployment

Image
Introduction In some cases, it becomes important to securely store key-value pairs, such as configuration data (e.g., usernames and passwords), rather than hardcoding them within a BizTalk orchestration. One effective way to achieve this is by storing these key-value pairs securely in the BizTalk SSO (Enterprise Single Sign-On) database and subsequently reading these values within our orchestration through a simple line of code within a BizTalk expression shape. In this blog post, we will go through the steps to add key-value pairs to the SSO database using the BizTalk Deployment Framework (BTDF). We will also explore how to read these values within a BizTalk orchestration and perform a simple BizTalk deployment using BTDF. Steps Creating a BizTalk Solution, Schema Project and Map project: Let's first create a BizTalk Solution called "SSOPOC" and a project called "SSOPOC.Schema". For this, you need to go to Visual Studio and click on File --> New Project --...
Read more