Where is Query Rules?

Prateek is correct.  Anyway you wouldn't want to create a query rule anymore - Query Entity rules (created within an expression rule generally) can do anything Query Rules would do plus more - and are a ton more flexible all-around.

Okay, sounds good. I created my query rule for "status" (shown below). This seems to be working correctly. Do you guys know how to use this to create the filter? Thank you.

What "filter" are you trying to create & where?

I would like to be able to select from the three drop-downs show belown (Status, LMI, Structure Type) and have the form sent to the relevant applicants who are correlated with the values I select. I heard I may need to use the query entity I made to do this, but I'm not sure how.

You would want to make your Query Entity rule accept inputs corresponding to all of those values, and preferably, query correctly whether or not each value is passed in (note that over-filtering may result in a returned list of zero people, depending on the particular data setup).  Assuming that you can derive Appian usernames from the result of the query, you could probably have your form map an array of usernames to a Rule Input when a submit button is clicked - and then pass that array out to your process model, where you could then call a subprocess for each user and assign the task therein to that user.  It's a complex use case and a lot depends on your particular implementation and requirements.

You would want to make your Query Entity rule accept inputs corresponding to all of those values, and preferably, query correctly whether or not each value is passed in (note that over-filtering may result in a returned list of zero people, depending on the particular data setup).  Assuming that you can derive Appian usernames from the result of the query, you could probably have your form map an array of usernames to a Rule Input when a submit button is clicked - and then pass that array out to your process model, where you could then call a subprocess for each user and assign the task therein to that user.  It's a complex use case and a lot depends on your particular implementation and requirements.

Ah, easy as pie. Thank you, Mike

Let's say a system got 100 + query rules created and been used in various design objects like (Process model - Script Tasks/IO Nodes, Expression Rules, Interfaces).Creating Query Entity and replacing them in such huge scenario is a hectic manual job. Is there any easy way (or) tool provided by Appian in such case ?

There isn't a way to bulk change existing query rules to a!queryEntity() because they are set up differently: Query Rules are Design objects, while a!queryEntity() is used in an expression.

That being said, your query rules will continue to work even if the query rule designer has been deprecated. If I were you, I probably would not worry about updating all 100+ rules. You could probably just update them as needed whenever you edit an object that uses them.

Thank you Peter for your response. Am really happy to see a reply from you, your Video Tutorials in Academy really helped me a lot to become an Appian Designer.

Have a nice day !