Search Applications, Objects, and Expressions


The Appian Designer, and the Application Designer, both provide search of their constituent objects. This article explains how to use the search functionality, and how it behaves.

Searching from Appian Designer allows you to search all Applications, and all objects, within that Appian environment.

Searching Applications

When you are viewing APPLICATIONS, your search string will be run against Application names and descriptions and return a list of all applications that contain the search string(s).


You can also use dates to limit your results to Applications based on when they were last updated.

Set your date filters in the the LAST MODIFIED section below the search box.

This will limit your results to all Applications that were last updated on or after the FROM date, and all that were last updated on or before the To date.

Searching Objects

When you are viewing OBJECTS, by default, your search string will be run against all object names, descriptions, and UUIDs (if the search string contains the full UUID), and return a list of all objects that contain the search string(s).

Search Expressions

After running your search, you can change the default search from Search Name and Description to Search Expressions. You will find these options in the upper-right corner of your search results.

Toggling your search to Search Expressions will run your search string(s) against the expression content of your objects.

In this search mode, the Description column is replaced with an Expression column that displays a snippet of the matching expression (or the first matching expression, if more than one is found in the same object). For example, a search for 17r1 would return a rule with a!facet_17r1( in the Expression column.

This search is conducted against the expressions in all design objects within your search set. This may be anything from a gateway expression in a process model, the definition of an expression rule, or the visibility expression of a record view.


You can filter your results by object type and last modified date.

Object Type

You can filter your object results by type from the OBJECT TYPE section under the search box. Simply select the object types to which you'd like your search results limited; selecting more than one object type will include those types in the results. When any object is selected in that list, all unselected objects will be excluded from the search results.

Last Modified Date

You are also able to limit your search results by when the object was last modified.

Set your date filters in the the LAST MODIFIED section below the search box.

This will limit your results to all objects that were last modified on or after the FROM date, and all that were last modified on or before the To date.

The Application Designer search works exactly the same as Searching Objects from the Appian Designer view, except the set of searchable objects is limited to those included in the application from which you are performing the search. This will also be true when you've opened a rule folder to browse its contents; any search your perform will only search objects found within that folder.

  • This search is case-insensitive, and treats all special characters as a space character. For example, the search terms apply( and apply will return identical results, as will the search terms CRM_getCustomerNames and crm getcustomernames.

  • Given this behavior for special characters, we automatically strip out Appian domains from the beginning of search terms to prevent confusion. Since the search a!applyComponents would be treated as a applyComponents, and therefore return more results than intended, we strip the domain and simply search for applyComponents. You can see the adjusted search term in the blue bar above your results.

  • When a search term is part of a longer word, it will only match if it matches the beginning of that word. For example, the search customer or customerFeedback will find uses of the customerFeedbackForm interface, but the searches feedback or feedbackForm will not, since the name of the rule does not start with those terms.