I have built a very similar use case to this with Fusion. In the one that I think works the best, we configured it like this.1. In the request form, there were several text fields. Each text field represented the type of deliverable they wanted, and then if they wanted multiple of the same deliverab...

I have automated this exact situation using Fusion, but AFAIK there isn't a way to do it with Workfront automatically.

2 things.1. The formatting for the heading would be #setParentID TASK name 2. I'm not sure if this will work or not, because the search could return multiple tasks, if they're all the same name. I am curious though, please let me know if it works.

You can replace text with {{emptystring}}, which is essentially deleting text, instead of replacing it with a space.

The easiest way is to run the string from the typeahead field in a parse JSON module, which will convert the string to variables you can use.

To make sure I understand, you are uploading a new document (or is it a document version of an existing document) to Workfront, the document is getting pushed to AEM as a version of an already-existing asset with the same file name in AEM already, but now the original asset in Workfront is gone? Pri...

This is for sure doable, my only concern would be if you have the same property on multiple tasks, how do you know which one is "right" to push up to the project?   Setting that aside, the way I would probably tackle this one is to setup a task webhook, and then if one of the properties you want to ...

That's correct, in the API call you have to create the OR filters, as you've described. A while back I thought this was bugged and asked Workfront and they're response was that it's functioning as intended. So now, for me at least, if I only include the unique filters in the GET request and then use...

Actually, I just thought of an easier way, since you're building it as an array. Create a variable (Not necessary, but it will make it easier to see what it's doing), and in that variable, add in {{add(emptyarray; {3.DE:D2D Account Lead - Creative};{3.DE:D2D Account Lead - Digital};{3.DE:HCG EG Stra...

Randy,   I know I'm a little late to the game on this one, but how I usually handle something this is IF({Property 1}!={null},{Property 1},;{empty string}. So then in the JSON string you would just have that 3 times, or however many properties you need.