That would be welcome, actually.I put a ticket in with support basically saying the same thing here and I have concerns about their potential solution. There is no way to disable these unwanted surveys without also having to disable:- Walk throughs- Deprecation notices- Help menu flyouts- Beta featu...

@KatherineLa wrote:I will also add that if a survey ever DID go to my entire user-base without permission, my next email to them would explicitly request that they DO answer the questions. But I would also ask them to answer with complete nonsense to make our data unusable.  @JohnJOSullivan perhaps ...

Hi again,So, I think the fact that I didn't know that these were coming from product--as opposed to marketing--is also an issue. There is a total lack of transparency when it comes to who is sending what when.This is more problematic when we've asked at least three times to stop doing this. This inc...

Thank you for validating this! As I mentioned, the threat of a survey right before we're launching an extremely important survey was infuriating.That said, as a company we would prefer that only sys-admins get those messages. I cannot tell you how many tickets we received about the API depreciation....

My goodness, y'all are tenacious: 

So, I logged into Workfront this morning and I was greeted to this:Oh wait, sorry, that wasn't it. It looked more like this:Now. We have begged Adobe, through our TAM, our CSM, and other acronyms to stop sending surveys to our users. And this one...I'm really hoping it only went to admins. I took th...

Exactly this. Works elsewhere but it doesn't work when using it for validation logic. I'm wondering if I do validation logic on a calculated field if that may suffice. Because as it is, I've stumped one of the foremost wizards with text mode, along with Grok.   -j

Oh man, sorry. It's been a day. If someone selects that field and something else, the system should prevent the form from being saved. Right now, we have "<Contract Name> - MUST BE THE ONLY CONTRACT SELECTED" as the value. And I don't know if it's an Aetna peculiarity, but no one seems to read.   W...

Sorry. What I'm saying is that Workfront is allowing me to save the expression. The syntax is correct but it's just not validating when I attempt to make it validate on a sample document.   

Hi friends,So, I have something which is driving me kinda crazy. I'm trying to write a validation logic rule where if a particular multiselect field is selected along with any other field that the validation error kicks in.Here's the formula:IF(ARRAYLENGTH({DE:fieldName})>1&&CONTAINS({DE:fieldName},...