You can pull all custom fields on a form by including categoryParameters:categoryParameter:name. That should give you a list of all fields on the form you searched for, and then you can do any comparisons you'd like to do.

So there's a couple of ways you can do it, up to you which method you go with. 1. Use the attachTemplate module, and include a simple array of all of the tasks you don't want to come over. If you already have all of the tasks you would want to copy over, this is relatively straightforward. Get a lis...

If you are just interested in, for example, the logo.png value, you would need to include get(array;1.Data.1.Properties.name). If you are wanting to iterate thru all of the "Data" objects, you need to iterate thru Array and then iterate thru Data, then you can just use Properties.name.

Unfortunately you can't remove inherited permissions with the production api (v19.0) or the api-unsupported versions. It is technically possible, but it requires using Workfront own internal API, that does not seem to have any guard rails that the standard API's do (or at least it didn't seem to las...

So if you already have fusion building the approval process, you just need to change the value in the userID field for that first stage approval to be the user assigned the issue.

Before I write too much, is your question more how to create an ad hoc approval on the fly with Fusion, or is it just how to put the assigned user into that ad hoc approval.

Unfortunately Workfront doesn't have the concept of a service account, only user accounts. You either have to include who the owner should be on creation, or you have to come in after creation and update the ownership.

It looks like your search (18) is returning multiple results. The "native" workfront modules in fusion include an iterator, so if your search returns more than 1 result, you will process all your downstream modules for each returned entry.   To correct this, a couple of things you can do, depending ...

If I recall correctly, it's available in the api-unsupported version, but not in the v19 version, specifically approverID or approver.

All good, glad you got it working. Have a good one!