New Experience - Allow Custom Forms to be Attached without Required Field Info | Community
Skip to main content
Level 4
March 5, 2021
New

New Experience - Allow Custom Forms to be Attached without Required Field Info

  • March 5, 2021
  • 1 reply
  • 289 views

In the Classic Workfront experience, there was a way to attach a custom form to a task without having to fill in the required field information. My agency has project managers add these forms to the appropriate tasks as new requests come up and then another team member fills the form in. Now we're switching people onto the new experience and realizing that all the required fields have to be filled in whenever a form is attached because there isn't a way to add a form without also hitting that requirement.


In our scenario, our project managers do not have the information that goes in those forms, they're just the person getting the form in place because they have the proper licenses. Another user with a work license generally has responsibility of filling in the form information and typically at a later date then when the task & form are added to the project.


Losing the functionality from the classic experience really hurts the process we had in place. And if the project managers just go in and add a bunch of dummy data to these required fields it means they're going to be triggering any reporting where users relay on these required fields HAVING information to pull into a report so they can count it as having been filled in for processing.

1 reply

JROatGeisinger
Level 2
February 24, 2026

@csatscale Our issue is similar to this older post.  We would like the Custom Form to be closeable without the Required Fields, as it is during the Request Process (with same form).  In other words, as a User enters a Request and has our Intake Custom Form to fill out, they can now leave a field blank.  When the PM converts the request to a Project, the PM must fill in dummy data or the Project will not save and close. How can we address that? 

CynthiaBoon
Adobe Employee
Adobe Employee
February 25, 2026

Hello!  For the previous post, there is an easy workaround in how that Custom Form is attached to a Task or a Project, in that if the Custom Form is added by clicking the Edit Task/Edit Project button, then unfortunately, any fields marked as Required have to be completed or it won’t save the changes.  However, if you go through the Task Details/Project Details tabs and add custom forms in the little box on the Nav bar, then they can be added without completing the form.

In this current issue, I think I need a little more information.  Are all the fields on the Custom Form attached to the Request Queue marked “Make a Required Field”? I’m just trying to understand how the requester is bypassing required fields.  If these fields can be left blank, is there a reason to have them marked as required at all?  I might be misunderstanding the question, so my apologies.  I tested it in my instance, and I unchecked all of the “make a required field” on the Custom Form, and I was able to convert Requests to Projects without having to fill in the dummy data.

However - just adding my previous experience here for a little added flavor. We had to require our users to fill out ALL of the required fields prior to converting to a project, even it is was a TBD situation.  (This was due to regulatory requirements.) Our workaround was to have Dashboards with Reports for any incoming requests that either had blank info (due to un-required fields) or TBD - with conditional formatting to quickly highlight what was missing or pending.  All of the PMs, Group Admins, and Sys Admins had these reports so we could quickly address missing data.  
 

I’m not sure if any of that is helpful, but if it’s better to email us at CSatScale@adobe.com to share more information, we can do our best to research further.  Thanks!

JROatGeisinger
Level 2
February 27, 2026

Cynthia - Amazing to get a direct response from the boss - You’ve nailed it, and I don’t understand why a User can get through that Custom Form leaving fields blank and can submit, but my PMs cannot covert tot a Project without adding dummy info.  FWIW, I did give thought to making no fields at all required.  Still might do that.