Expand my Community achievements bar.

The next phase for Workfront Community ideas is coming soon. Learn all about it in our blog!

Prevent Task from Being Marked as Complete If Required Fields on Custom Form Attached to the Task Are Blank

Avatar

Level 9

8/15/17

Right now, if a custom form is attached to a task, there is nothing that forces the user to fill out the custom form. The task may be completed, without the custom form from being updated. Even if the custom form has required fields. Only when someone edits the custom form, does it require you to fill in the required fields.

We have examples of collecting information when we get to certain points in a project. This data is being collected via a custom form on a task. However, the system doesn't force the assigned to user to fill in the custom form. They can close the task without even looking at the custom form tab.

As a workaround we have been attaching an approval process to the task, so the PM can verify the information was populated. However, it would be nice to not have to take this extra step.

15 Comments

Avatar

Level 2

10/17/22

This is something that is crucial to our users and agree is a basic requirement. Could we escalate this? As said above, this was raised in 2017!

Avatar

Level 1

10/24/22

We've had to configure Fusion scenarios and approval tasks in order to ensure users are completing mandatory fields within custom forms and tasks before being able to close it - it does seem to be strange behaviour that mandatory fields need to be policed this way! It would really help to simplify our configuration if an enhancement could be made to the product to fix this.

Avatar

Level 4

12/20/22

This functionality would be a win for our teams, too. It's not exactly a "required" field if a user can close the task without filling out said field!

Avatar

Employee

1/10/24

Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!

 

Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.

Status changed to: Declined