I haven't seen this behavior yet in our instance. I'm curious if the folks that are experiencing it have converted to the new Admin Console/Unified Shell or are you still regular WF? My instance hasn't converted yet.

I'm not sure on that part, mainly because you say the behavior is occurring at many points in the UI. That suggests something that all those UI screens must have in common. The only thing that comes to mind would be your Branding configuration images, whether at the instance level or at a layout-tem...

This would be insanely obscure, but I do know that when a browser tries to download a file and finds it corrupt/unreadable then it will often download simply as a 1kb file. Does your instance have custom branding, or use any sort of custom icons/images for navigating in things like reports/dashboard...

What is currently live is a single scenario that watches for new Issues in a specific queue and immediately raises a paired Issue in an appropriate project for Jira, then copies over all the custom fields and documents. At this time, we've decided not to allow WF updates to push to Jira to avoid cha...

I haven't seen precisely that scenario myself, but it almost sounds like it got confused about which 'you' was 'you' and somehow loaded a cached earlier version of the form. If you want to see all the recent edits to a form, you can look under Audit Logs for the Log Types 'Custom Form', 'Custom Fiel...

I don't know pricing, but that's currently called WSA or WSA(F) if you have Fusion support. I have hours for my support with both an Admin and a Fusion dev.

Cascading drop-downs can be accomplished with the External Lookup fields, though they are definitely fiddly to configure. For example, in my instance we have a "Product Family" field, and I needed a second drop-down where the user could select which Product Type the Project corresponded to but I wan...

Once created, the key and 'equates with' settings cannot be changed even by the full admin. Your only option is to delete and start over. Mine matched because I knew what I needed them to be when I set them up originally. Your guess on the Group Admin is likely also correct. As our instance-admin, I...

That would read as valueexpression={project}.{template}.{name}  For valueexpression formulas, you need a period between the fields rather than a semi-colon. That's usually what trips people up when they're learning.  Here's a good overview: https://experienceleague.adobe.com/en/docs/workfront/using/...

In my instance, I replace the valuefield=<field> portion of the field defintion with valueexpression={field} instead. By making the field display as a calculated field instead, the text is visible to all users and not just those with access to the underlying object. It does have the side effect of m...