Searching the specific string in array values of constants

When an expression runs, all constants get evaluated to their set value which in this case is a List of Text. You should have no problem finding a specific string in an array of text. Can you provide an example expression which isn't working?

My assumption was that he's referring to the /design "search by expression" functionality, which in fact does not return results of constant values as far as I've been able to tell, much to my occasional frustration.

Thanks Danny / Mike,

Yes Mike is right. I'm looking to scan the content of constants using the search string. Although search by expression is possible, however to search inside the constant values, only option seems to download the constants objects as a package and use standard  windows search tool to scan xml files. I'm trying to find the specific email-id value where its referred in the application objects / application settings.

I suppose the technical answer from the Appian side would be, that constant values are not included in "search by expression" because constants don't actually contain any "expression" code (just literal values).

It's still counter-intuitive, since it seems such functionality (or something very similar) should have the ability to let us scan for problematic labels, emails, id values, etc, in a large production system - where the same values would be easyish to find if they'd been hardcoded into their respective interfaces or expression rules.  As I said, this has troubled me on several occasions, and I still don't know of any easy workarounds, other than the one you mentioned already.

I suppose the technical answer from the Appian side would be, that constant values are not included in "search by expression" because constants don't actually contain any "expression" code (just literal values).

It's still counter-intuitive, since it seems such functionality (or something very similar) should have the ability to let us scan for problematic labels, emails, id values, etc, in a large production system - where the same values would be easyish to find if they'd been hardcoded into their respective interfaces or expression rules.  As I said, this has troubled me on several occasions, and I still don't know of any easy workarounds, other than the one you mentioned already.

Thanks Mike,