Betreff: Ho to create a proof with AdvancedProofing Options in Workfront Fusion?

[BidkarLe]

I am working on a process flow to create a proof based on the document on a task but I want to also modify the details of the Proof which can only be done via the advancedProofingOptions at the bottom of the Misc Actions modules. I found that a Json string must be passed on to this field but I have been trying the example given in Experience League and it does not work. Is there a documentation on how each field should be mapped on to the Json string? such as Name, Email, etc..

[lgaertner]

Hello BidKarLe,

On my instance it is working using the Misc Action Module with the action createProof and a JSON in the following format in the field advancedProofingOptions:

{
    "stages": [
        {
            "name": "TestStage1",
            "lockOn": 1,
            "position": 1,
            "isPrivate": false,
            "activateOn": 1,
            "recipients": [
                {
                    "name": "",
                    "role": 5,
                    "email": "test1@test.com",
                    "recipient_id": "",
                    "notifications": 0,
                    "isPrimaryDecisionMaker": null
                },
                {
                    "name": "TestStage2",
                    "role": 5,
                    "email": "test2@test.com",
                    "recipient_id": "",
                    "notifications": 0,
                    "isPrimaryDecisionMaker": false
                }
            ],
            "isMandatory": false,
            "deadlineDate": null,
            "deadlineTime": null,
            "isOneApproval": true,
            "activateOnDate": null,
            "parentPosition": null,
            "activateOnDecision": null,
            "deadlineCalculateOn": null,
            "deadlineBusinessDays": null
        }
    ],
    "message": "This is a Test",
    "subject": "Test using Fusion",
    "templates": [],
    "hasMessage": true,
    "canDownload": true,
    "customfields": [],
    "hasPublicSharing": true,
    "isAutomatedWorkflow": true,
    "stageBasedVisibility": 0
}

Regards

Lars

[lgaertner]

Although the proof is created not all parameters from the JSON seem to be considered...

Hmm. I need to investigate this further some time, but as described in the last note box in the linked Experience League document, Adobe wants us to play around with the proof module to find out how to setup the parameters...

[BidkarLe]

For this example, is it properly setting the two reviewers that you are specifying? That is what I'm mostly concerned about. 

[BidkarLe]

This is what I get after trying a very similar Json text to yours 

And this is the json that I used just replacing the email for the people I want for reviewers on my proof.

{
    "stages": [
        {
            "name": "TestStage1",
            "lockOn": 1,
            "position": 1,
            "isPrivate": false,
            "activateOn": 1,
            "recipients": [
                {
                    "name": "",
                    "role": 5,
                    "email": "user@mydomain.com",
                    "recipient_id": "",
                    "notifications": 0,
                    "isPrimaryDecisionMaker": null
                },
                {
                    "name": "Workfront User Name",
                    "role": 5,
                    "email": "usern2@mydomain.com",
                    "recipient_id": "",
                    "notifications": 0,
                    "isPrimaryDecisionMaker": false
                }
            ],
            "isMandatory": false,
            "deadlineDate": null,
            "deadlineTime": null,
            "isOneApproval": true,
            "activateOnDate": null,
            "parentPosition": null,
            "activateOnDecision": null,
            "deadlineCalculateOn": null,
            "deadlineBusinessDays": null
        }
    ],
    "message": "This is a Test",
    "subject": "Test using Fusion",
    "templates": [],
    "hasMessage": true,
    "canDownload": true,
    "customfields": [],
    "hasPublicSharing": true,
    "isAutomatedWorkflow": true,
    "stageBasedVisibility": 0
}

[FrankFi1]

Hi @BidkarLe ,

found the solution in stackoverflow: https://stackoverflow.com/questions/77298930/workfront-restful-api-endpoint-payload-for-initiating-a...

You have to use the Misc Action Module with the action createProofRest and add this JSON (Without the comments)

{
    "stageBasedVisibility": 0,
    "hasMessage": true,
    "message": "",
    "isOneApproval": false,
    "subject": "",
    "hasElectronicSignatures": false,
    "hasPublicSharing": true,
    "customfields": [],
    "hasCustomMessage": false,
    "isLoginRequired": false,
    "templates": [],
    "hasSelfClose": false,
    "canDownload": true,
    "hasSubscription": false,
    "stages": [
        {
            "deadlineDate": null,
            "isPrivate": true, //
            "lockOn": 3,
            "isMandatory": true,
            "parentPosition": null,
            "activateOnDecision": null,
            "deadlineTime": null,
            "name": "Stage 1",
            "deadlineCalculateOn": null,
            "deadlineBusinessDays": null,
            "activateOnDate": null,
            "isOneApproval": true,
            "position": 1,
            "activateOn": 1,
            "recipients": [
                {
                    "permissions": {
                        "shareProof": true,
                        "resolveCommentsAndActions": true
                    },
                    "role": 3, // This is the users role
                    "email": "**USERS_EMAIL_ADDRESS_IN_WORKFRONT**",
                    "isPrimaryDecisionMaker": false,
                    "recipient_id": "",
                    "notifications": 9, // This is the users notification type
                    "name": ""
                }
            ]
        },
        {
            "position": 2,
            "deadlineCalculateOn": null,
            "isPrivate": false,
            "deadlineTime": null,
            "isMandatory": true,
            "activateOnDecision": 1,
            "activateOnDate": null,
            "activateOn": 8,
            "recipients": [
                {
                    "permissions": {
                        "shareProof": true,
                        "resolveCommentsAndActions": true
                    },
                    "role": 5, // This is the users role
                    "email": "**USERS_EMAIL_ADDRESS_IN_WORKFRONT**",
                    "isPrimaryDecisionMaker": false,
                    "recipient_id": "",
                    "notifications": 5, // This is the users notification type
                    "name": ""
                }
            ],
            "lockOn": 3,
            "deadlineDate": null,
            "name": "Stage 2",
            "isOneApproval": true,
            "deadlineBusinessDays": null,
            "parentPosition": 1
        }
    ],
    "isAutomatedWorkflow": true,
    "parentFileToken": null
}

Adjust the settings to you needs.
For me it works totally fine.
BR
Frank

[simplykevinm]

Hi @FrankFi1, do you have any idea on how to leverage pre-defined workflow templates in workfront to create the automated workflow? i can see there is a parameter for "templates" but not sure on how to use it. Any leads are helpful. Thanks

[Raymundo2]

Curious if anyone has successfully used this to set the Proof Workflow Stages, whether just a Basic Proof Workflow or referencing an Automated Proof Workflow?

I am able to create the Proof as needed, but this API does not appear to be applying the basic or automated workflow currently. Any tips?