I'm still not understanding but we have a dropdown field called "Show/Hide" and if you select "Show", all the other sections on the form become visible. We have it defaulted to "Hide" and the sections are all hidden. That's all I can think of.

@RAshley  next time, just use the preview sandbox. This refreshes every saturday night whether or not your governance board likes it.

oh good. I was wondering. If you refresh the sandbox does the user go away or stay?

I personally don't believe there's a way to automatically attach a form just because someone looked at a page, but good luck with your search.

I know that it's on the Workfront roadmap to allow permanent deletion within a workfront instance, but I don't see it active in my environment as of today. We can and do remove them from adobe console, and look forward to removing them from workfront when we arrive at that point again.

No. Just create a report that has all 3 test columns, and put in some formatting that will make the relevant one light up (i.e. format the cell background for column "test B" to be green if test area was set to area B) 

You can use Fusion to do this, and it is the only way you can do this to documents.   For the rest of the objects like tasks, issues and projects, we attach the form from the start by using all templated methods such as project templates, request queues (queue topics), and the project settings relat...

You should talk to Support. I think your workaround would be to test it in one of the sandboxes. This way your junk users are overwritten the next time you refresh. But I don't understand for sure how that all works, so it's just best if you confirm with an expert.

If you can't get it working, try using the same approach as this post: https://experienceleaguecommunities.adobe.com/t5/workfront-questions/reporting-on-typeahead-fields/m-p/504877   Add your calculated field to the project level and then reference that field on the task level.

This looks like a rich text field -- as far as I know, you will not be able to use the same sort of truncation valueexpression with these types of fields.   Have you considered using just a normal Paragraph field? you'll be able to truncate using this. I guess it comes down to what your users priori...