Workfront Custom Form | Community
Skip to main content
Level 2
March 15, 2026
Question

Workfront Custom Form

  • March 15, 2026
  • 1 reply
  • 15 views

Hi everyone,

I’m trying to implement a Portfolio → Program dependency in Adobe Workfront and ran into a behavior that I’d like to understand better.

Background

In the native Workfront project fields, Portfolio and Program already exist as built-in fields. When we create a project:

  • Portfolio can be selected

  • Program automatically shows only programs related to that portfolio

This dependency works perfectly.

However, the problem is that these native Portfolio and Program fields are not required fields, and Workfront does not allow us to make them required.

What we tried

To make these fields required, we created them again in a Custom Form using reference fields:

  • Portfolio field

    • Reference Field: Portfolio

    • Set as Required

  • Program field

    • Reference Field: Program

    • Set as Required

The goal was to force users to select both Portfolio and Program when creating a project.

Issue

After creating these fields in the custom form:

  • When we select a Portfolio,

  • The Program field still shows all programs, instead of only the programs related to that portfolio.

So the native dependency (Portfolio → Program) is not working in the custom form fields.

Question

Is there a recommended way in Workfront to:

  1. Make Portfolio and Program required fields

  2. Maintain the automatic filtering of Programs based on the selected Portfolio

Has anyone implemented this successfully, or is there a best practice for enforcing required Portfolio/Program selection while keeping the dependency intact?

Any suggestions or guidance would be greatly appreciated.

Thanks!

1 reply

Kurt_Jones
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 15, 2026

Abisheik,

If you have Fusion you could, based on fields users fill out on the form, have Fusion populate the Portfolio and Program for you when it converts the request to a project template, choosing the Portfolio and Program based on items on the form.  This is highly dependent on your company’s processes, it may or may not work for you.  Another avenue that teams will choose, again, based on your company’s processes is populating Portfolio and Programs as part of template set up, again, this may or may not work, but its an option.

For your #2 option, you could use an External Lookup field where the choice from the Portfolio field is the dependency for the Program external lookup field.  This will allow on the programs related to the Portfolio that was chosen to show for the user to select.  Here’s a link that shows examples on the external lookup field, https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/customize/custom-forms/design-a-form/external-lookup-examples

If my response answered your question, please mark it answered, so others can find the answer
Level 2
March 16, 2026

Hi Jones We tried a various combination on 2 option but we cannot fetch the programs that related to portfolio can you provide “Base API  URL “and “json format”.

Kurt_Jones
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 16, 2026

for example below, I’m assuming your portfolio field is called “portfolio”.  api would look something like below:

Base API URL

$$HOST/attask/api/v20.0/prgm/search?portfolioID={DE:Portfolio}&fields=name

Dependencies

{DE:Portfolio} 

JSON Path

$.data[*].name

 

This should show the names of the programs based on the portfolio item that was chosen in the custom field for portfolio.  Just use the name of your custom field in place of DE:Portfolio, example, DE:name of your portfolio custom field

If my response answered your question, please mark it answered, so others can find the answer