Sure thing, here's the general outline/setup. To start, this particular queue is one that external customer users log into in order to ask for various items. We needed a form for them to fill out, but also a form for the internal team to track updates and other details that didn't need to be custome...

This is an odd one, but are you a full admin in your instance? I think I recall seeing that behavior when someone was trying to copy a project that contained/referenced something they didn't have the security rights to see. If you aren't a full admin, see if yours will do a screenshare and compare w...

Here's a couple quick ones from my instance -    Automated OOO responses - Watch update messages, assess tagged users versus active delegation rules. If matched, post comment tagging delegatee, and comment back with information on when the original person is expected to return.Auto-attach commonly f...

In that scenario, I create two forms and carefully manipulate the sharing settings so the external users can't see the second form. We've got a few queues that work that way in our instance. You can attach both to the queue default form setup at once, and as long as you share the forms correctly, th...

I've written a scenario in Fusion that does what you're describing, but there's nothing natively provided that will auto-tag a delegatee or notify the writer that someone is OOO natively at this time. 

Just finished writing that up here! https://experienceleaguecommunities.adobe.com/t5/workfront-blogs/sneaky-sys-admin-shenanigans-tricking-project-templates-to-only/ba-p/776614

Do you struggle with team members who create new stand-alone projects from ad-hoc task templates? Do you wrangle the inevitable support tickets to fix the resulting data issues?  Read on for a sneaky way to use field-level validation entirely incorrectly, and save a bit of your sanity in the process...

Sure thing. These columns would be used in a report built on the Report object. They are NOT particularly human-readable, but they give me the ability to search by API Field name for things that would be hard to find otherwise.    For all fields displayname=View valuefield=view:definition valueforma...

The nuance between 'assigned to ID' and 'assignment users ID' is one that drove me nuts until I understood it too.

I need to pick just one?!?    As an admin, I'd say that finding a way to create a report-report that shows me the full code underneath every view/filter/grouping for the report has saved a ton of potential issues. I've been able to build exception reporting based on that to show me where people are...