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..
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
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
Views
Replies
Total Likes
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...
Views
Replies
Total Likes
For this example, is it properly setting the two reviewers that you are specifying? That is what I'm mostly concerned about.
Views
Replies
Total Likes
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
}
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies