Skip to main content
Level 3
June 17, 2026
Question

Workfront Planning Automation

In Workfront Workflow, we currently use several multi-select fields to define our project types.

When someone submits a Campaign Request form, they first choose an overall element type—such as Digital, Social, or Email—and then select a more specific option tied to that category (e.g., Digital Type, Social Type, Email Type).

I’m trying to determine how to replicate this setup in Planning for automation without resorting to one long, combined list of all element types. If we go that route, users would have to scroll through an extensive list just to find the correct option when generating a project.

Any suggestions? 

3 replies

Madalyn_Destafney
Community Advisor
Community Advisor
June 17, 2026

Hi there, if you add a request/intake form on your record type as a way to add new records, you can apply display logic on those record fields in your planning form, so you could have different Qs show only if other values in other fields are selected to help guide the user thru record data.

 

If you don’t want to use a form, the notion of cascading fields or dependent picklists is in the works, where based on the value you select in one field, the values offered in other fields change/narrow instead of showing all options. I think this is more what you’re after, and I think it’s likely coming in late Aug/early Sept.

Translate
If this helped you, please mark correct to help others : )
MelanieM1Author
Level 3
June 17, 2026

Hi Madalyn—thanks so much for your reply!

I added a custom form with logic applied, but I’m struggling to see how to configure Planning so the automation creates the project based on the element the user selected on that form.

From what I can tell, Planning automations can only be configured off a single field. Because of that, I’m not seeing a way to make this work unless all element options live in one consolidated list—which is what I’m hoping to avoid.

Translate
IvanCyber64
Level 2
October 9, 2026

Hi ​@MelanieM1 ,

I can see that this question is from three months ago so you already probably noticed that you are not limited to one field when triggering automations. Now you can do that, please check the following screenshot

One limitation there is is that at the moment we can only do and conditions and not or, so this might not cover all of the cases, but this also might be implemented soon.

Best regards,
Ivan Bebek

Practice Lead Work Management

CYBER64
Adobe Gold Solution Partner

Translate