Prevent Task from Being Marked as Complete If Required Fields on Custom Form Attached to the Task Are Blank | Community
Skip to main content
jerflo
Adobe Employee
Adobe Employee
March 5, 2021
Question

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

  • March 5, 2021
  • 6 replies
  • 2862 views

Hello my community friends. I am looking to get some feedback on this idea. If interested, please schedule some time with me using the link below. We can delve deeper into this, share screens, and talk shop.

https://calendly.com/jeremyflores

6 replies

MoniqueEvans
Community Advisor
Community Advisor
March 5, 2021

This would be SUCH AN AMAZING FEATURE!!! I would prefer this live on the project level, but task is a good start. I have so many exception reports that call this out but still have to police this so we have data filled in. Being able to force the project to stay open will create an annoyance (in a good way) to the users on the project team that tell will actually be compliant

Level 10
November 17, 2021

Task-level and project-level, set separately, would be welcome.

RandyRoberts
Community Advisor
Community Advisor
March 8, 2021

Could this just be part of form validation?

jerflo
Adobe Employee
jerfloAdobe EmployeeAuthor
Adobe Employee
March 11, 2021

@Randy Roberts‚ tell me more...

cc. @Gevorg Kazaryan‚ what are your thoughts here?

RandyRoberts
Community Advisor
Community Advisor
March 11, 2021

@Jeremy Flores‚

I thought I heard something somewhere about Workfront being interested in doing some type of form field validation. Like If you have an email field it would check to make sure it included one or more characters followed by an @ symbol followed by more characters followed by a dot followed by a few more characters.

I can't remember where I heard it though, or maybe it was a suggestion in the innovation lab.

Either way, it's a really good feature to have.

Edited to add: This is probably what I was remembering:

https://one.workfront.com/s/idea/0870z000000PSEhAAO/detail

Back to the original post, Workfront already does this on a project level. If a required project field isn't populated, you can't open the project. I think doing this in reverse (can't complete it) with a task is worthwhile. Although it shouldn't prevent you from marking the task as something that equates with complete (CPL), like waived or cancelled.

Level 10
March 12, 2021

@Jeremy Flores‚ , are still seeking feedback this idea? (I'm catching-up on back-reading of digests‚Ķ)

jerflo
Adobe Employee
jerfloAdobe EmployeeAuthor
Adobe Employee
March 14, 2021

Hey @Kevin Quosig‚ - yes, still looking for additional takers on this one. Also, would it be more beneficial to have this at the Project level first?

Level 10
March 15, 2021

I think project-level first for us, since there is mandatory financial information that gets skipped. Though I could see uses of the task level too, if it were available.

jerflo
Adobe Employee
jerfloAdobe EmployeeAuthor
Adobe Employee
March 17, 2021

@Kevin Quosig‚ at what point in the process does this information get skipped? Are there certain points in the process where you would need this validation? Thanks again!

Level 10
March 18, 2021

Specific examples elude me at the moment in NWE, but in Classic we had cases where a user started a project without one of our templates, which menat without some custom forms that are required for various financial info and tracking.

Adding these forms after-the-fact did not seem to kick-off the filling out of the form.

Another example I just thought of: what if we need to make change to a custom form that requires a new custom field, and that field is mandatory? Having a way to force the field to be filled out would be very useful.

Level 2
November 16, 2021

Hello @Jeremy Flores‚ we are looking for a similar feature. I guess this can be done via Fusion. But is there a way to do it without fusion. As our request submitters are asked to manually add a custom form to a task before submitting it to reviewers, they forget sometimes and hence causes back n forth and mess.

Do you think we have a solution already for this type of use case.

Thanks in advance.

FYI @Agnieszka Markuszewska-Shehata‚

jerflo
Adobe Employee
jerfloAdobe EmployeeAuthor
Adobe Employee
December 1, 2021

Hi @Juhi Kanjani‚ - thanks for your message. There is not a way to do this natively without fusion, unfortunately. Admittedly, I was working on a solution around the time of this post but had to prioritize other items ahead of this so this got pushed to the bottom of my backlog. I'm sure at some point we will revisit this I just don't know exactly when that will be.

Kundanism
Level 10
November 16, 2021

Hello @Jeremy Flores‚ . this will be a very useful feature in Workfront native, in addition to Fusion. I agree with above users too.

Mvh

Kundan.

jerflo
Adobe Employee
jerfloAdobe EmployeeAuthor
Adobe Employee
December 1, 2021

Thanks @Kundan Kumar‚ - I'm glad to hear that there is still interest in having a capability like this.