In the example HERE, it shows the equals comparison as a double sign. Have you tried that one yet? I know I have some with '!=' working as expected.      

You're very close I think. Give this edit a try to start. You have to at least give if the 'false' criteria for sure.   IF({DE:Who is creating your communication?}="pods","Pods-based materials cannot be reviewed in this queue.","")   If that still doesn't work, check: 1. Case sensitivity - Is the dr...

I think I almost have my holy-grail of features here. Hoping someone else can close my gap on Scenario Three below to make it perfect.   In my instance, the use-case 'Can we make that field required for only company XYZ?' is incredibly common, and one I've not been able to support without creating e...

The only other obscure option could be if the admin has dragged those options way down in their navigation menu so they're below everything else, and for some reason their browser isn't showing them the scroll down menu. But otherwise once you're a Sys Admin, the only way I know of to hide anything ...

The other thing I'd check is that the Program is Active. I've run into that a few times in our instance.

Put a ticket into Support. I ran into that too, and when you delete a status sometimes it doesn't fully release the Key you previously used somewhere in the database. They can fix it for you though. I can look up whatever my ticket number for it was if they aren't sure how to help initially.

Each record in WF has an associated reference number, but I wouldn't expect the reference number of the original issue to change. The resulting project would have it's own separate reference number though. Are you seeing the original issue's number changing? 

This is worth trying to fix, we've definitely had a couple cases where an internal employee tagged an external customer from the wrong customer in a discussion by accident. I've seriously considered branching access levels so only people who work with external customers can even see them in the list...

We use them periodically for different things. The one sticking point we've run into is that for some reason, those specific emails get routed to Junk Mail a LOT by Outlook, even when all the ordinary notifications coming from the same email arrive just fine. I finally put together this single slide...

So the solution to fix what they broke is to pay them for hundreds of unnecessary new licenses. That's...convenient. Looks like I need to start evaluating other vendors to handle our request queue functionality soon.