Gotcha -- If that's the case then, my initial thought here would be to use the Array Aggregator module and then deduplicate() to remove the duplicative values from the list.

Heya! So, to confirm, is the output result you're looking for just one big list of emails versus the separated bundles? So something like: email@email.com, email1@email.com, email2@email.com ?

As of now, I don't believe there is an out-of-the-box Fusion module for AEM Sites the same way there is for AEM Assets. Adobe does provide a Workfront–AEM Assets connector, but for full AEM Sites integration (like, creating pages or triggering AEM workflows from Workfront), you will probably need to...

You can't set it to 'null,' but you can replace it with another date. If you set it to null, it'll just keep the original commit date. 

It sounds like you’re running into a classic time zone mismatch in Workfront. Even though your tasks are set for 5 PM EST, Workfront still uses UTC under the hood, then converts display times according to both the system time zone (your organization’s main Workfront setting) and each user’s personal...

As far as I know, there isn’t a strict, documented “maximum fields” limit for Workfront’s “Read a Record” module in Fusion, but in practice, large field selections can cause errors—usually because the request payload ends up being too large or takes too long to process. The only listed limit I know ...

Hey @ConnorO2 -  From what I'm seeing here...You're getting that error because that module doesn’t know which project (or object) to attach that update to. So that's why it's telling you the “objID” parameter is missing. I'm assuming you're using the "Update" Record Type? There should be a checkbox ...

Ok, gotcha. I have a similar setup in terms of reading a large number of projects, but mine is attaching data versus removing data. I just did a quick draft, so my recco would be:  1. Set up a search module to look up projects that have an entry date of 30+ days (or documents belong to projects of m...

Hi @TroyCu - Would this need to be an ongoing automation for all future projects (ie: always search for projects that match this criteria, run the scenario)? Or a one-time deal for one particular project?

By "create a new user" do you mean generating a new user directly in the Workfront enviro and not Admin Console? If so, yes, so long as it's not a SysAdmin access level you're trying to generate/update/etc. Everything else can be customized via Fusion.