Here's an option you could do.1. Setup a second Fusion scenario using a custom webhook. This scenario should include everything that you want to do with the document, so downloading/uploading/pause/metadata etc. Note: one of the first things you'll have to do is provide a 200 response with the webho...

I've worked on a similar use case before, and the way we approached it (right or wrong) was to have a type-ahead field for each portfolio's programs, and only show the typeahead required based on their portfolio selection. Unfortunately, you can't dynamically filter the typeahead based on another se...

Your call is incorrect.URL: {your workfront api URL}/OPTASK/{issue ID}Method: PUTQuery String: action=convertToProjectIn the header, include apiKeyIn the body, include this JSON:{  "project": {    "name": {project name},    "templateID": {template ID if desired  },  "options": [    {any options you ...

Add to your query string fields=currentVersion:proofID,currentVersion:proofStatus

Sorry, forgot one thing on that JSON. It should be this:{"accessRules": [ {everything from above} ]}

John, Try this.Create a JSON with this structure:{ "objCode": "string", "accessorID": "string", "coreAction": "string", "securityObjID": "string", "accessorObjCode": "string", "forbiddenActions": ["string"], "secondaryActions": ["string"] } How to fill out the json:objCode: ACSRULacces...

That wouldn't work. The ability for Workfront to have OR statements in webhooks is fairly recent (like within 2-3 months) and unfortunately that functionality hasn't been added into Fusion's webhook builder. Instead of using the native Workfront webhook, you could use a custom webhook, and then crea...

You can, but it would be easier to just use a typeahead field. Are you unable to use a typeahead?

If the requestor is always modifying the original request, then here is what I would do.setup a webhook to watch for issue modifications on issues from your request queue, and that have been converted to a project. This will let Fusion know that an update has occurred.Determine what changed. Because...

The "shouldCreate" key isn't a thing. Take that part out.Edit: IIRC you also need to provide a value in the approvalType field, and I don't think sequenceNumber should be sent either.