Using queries

In the Business console, you use queries to search for elements of your projects. You can apply actions to the results of the query.

With queries, you can filter business rules or other project elements. You can perform actions to all the results of a query, or only to specific results. For example, if you have a modification to apply to a certain type of rule, you can create a query that searches for the rules corresponding to this type and modifies them. You can also create queries to find which rules have been affected by any modification you made.

You can also use queries to extract rules for generating a ruleset. To use queries as an extractor, you must define the query to use in a decision operation.

Queries are made up of two parts:

  • The query part, for example, Find all business rules such that the creator of each business rule is me

  • Optionally, an action part, for example Do set the status property to deployable

You construct queries in the same way that you construct rules, with a condition, and optionally an action. The default query action is to display the results, but you can also have the query carry out other actions such as moving the results of the query to another folder.

Queries are run against the current project, as well as any linked projects if you specify this option. Queries apply to the current branch, release, or change activity where you run the query.

New in 8.10.2 To search for specific types of rule artifacts you must use the correct rule type in the query part, according to the following rule hierarchy, which includes technical rules and functions since V8.10.2:

Figure 1. Rule hierarchy

Image shows the rule hierarchy

For example:

  • Find all rules returns all action rules, decision tables, and technical rules.
  • Find all business rules returns action rules and decision tables.

To run a query on functions, you must explicitly state it in the query part: Find all functions.