The interface has become significantly worse within the past year. It now takes me 5-8 minutes for the execution history of the simplest automation to process. The new Workfront modules are extremely difficult to work with. (I hope the legacy modules remain as-is.) I'm trying to do some off-the-cloc...

This is an old thread, but I have a question. I'm attempting to do something similar with a calculated field which concatenates a URL. The code above doesn't work for this, but it has worked with a field which is a single line text field.  Assuming/guessing that calculated fields don't allow for thi...

So once we created the Adobe ID account, we relinked it both within Workfront and Workfront Fusion. We had to recreate the connections in all of our teams. Then we had to use the Dev Tools to transfer that new connection to all other Workfront modules in the scenarios.  It sounds like a lot but it w...

Description: It's pretty straightforward: Make it so the status field is editable on the My Requests widget. Why is this feature important to you: We are on a crusade to remove clicks wherever possible. Right now, if I want to change a request's status in the My Requests widget, I have to select the...

That is wonderfully silly! I love stuff like this.  I will have to think how to incorporate the Hyper-Text Coffee Pot Control Protocol into things now. -j (not a teapot)

Oh for Pete's sake. Yeah, I look at the form in real life and the validation error occurs. That's what I get for trying something new EOD. Thanks for all your help! -j

The Sharepoint thing is...a larger problem--apart from Fusion alone. But at least we've got most of it working again. But if I had hair I'd have been ripping it out of my head.  But at any rate, I *love* this! I'm a big believer in making Workfront feel more "human." Our Fusion-based notifications r...

The thing is that it's doing nothing. The hope: The validation error will occur if someone chooses one of the choices in a single-select dropdown list.I did a test field with four dropdown values. In this test, I want "C" to elicit the validation error: I tried that with two equal signs, one equal s...

Everything is as it needs to be. Field name is used, the value for the field is lower-case-p "pods." The only thing I didn't include in my example is the else you added with the comma...which I tried before.  That's what's killing me. It's so simple and there has to be something off.  

I must be doing something stupid because my use case is very simple. I have a single-select dropdown on a form. And if someone selects "pods" from this field, I want a message stating that Pods-based materials cannot use that queue. (This is my intended workaround against being able to hide some opt...