Find tool — Search syntax and stop words |
When enabled, Process Commander maintains search indexes to
support rapid operation of the Rule content
and Work objects
searches in the Developer
portal Find tool. These indexes also support the Find Content
panel in the Advanced Search tool.
Use the syntax to define sophisticated, focused searches.
By entering appropriate syntax, you can search for property values containing combinations of words, rather than single words. For example, you can search for all the activity rules that contain the phrase "Mary Poppins" or that contain both the word Mary and the word Poppins in a single property value.
A word starts with a letter A-Z or digit 0-9 and contains only the letters, digits 0 to 9, dash, and underscore characters. If the word includes a dash or underscore, surround it with double quotes. Case is not significant. For example:
Some common words are normally not searchable; these are known as stop words.
You can enter a search term that contains non-ASCII characters — in fact, any UNICODE character — but English definitions of white space and word breaks apply.
Use the operators and notation to enter powerful search queries. Six operators are supported:
Double quotes to exactly match a phrase of more than one word, or a word containing any dash or underscore characters
Binary operators AND and OR (always uppercase)
Unary operator NOT (always uppercase)
Asterisk character for wildcard suffix
Parentheses to determine operator precedence
Tilde for a "sounds like" suffix
Use the NOT operator with at least two words. That is, you can search for Red NOT Tall; you cannot search for only NOT Tall.
The operators can be used in combination.
To produce fewer matched results (hits) to review, enter a more detailed query. This does not slow the search processing.
For example, the search statement:
(green OR blue) AND NOT (yellow AND white) AND viol*
matches an instance that contains this property value:
The green viola jumps the lazy dog.
but does not match an instance containing:
The blue light violently turned to yellow then white.
The search statement:
"late payment"
matches late payment but not latest payment, late payments or payment late, or late as one property value and payment as another.
Certain words that appear frequently in English text, HTML code, and Java code are automatically ignored when you submit a search, as they would otherwise expand the index substantially but provide little added precision in searching. For example, because ELSE is such a word, searching for LITTLE AND ELSE is the same as searching for LITTLE.
To force the search to include a stop word, include the word in double quotes:
LITTLE AND "ELSE"
The stop words include single digits 0 to 9 and the following:
a | abstract | and | are | as | at | b |
be | body | boolean | break | but | by | byte |
call | case | catch | char | class | com | const |
continue | default | div | do | double | else | embed |
extends | false | final | finally | float | for | form |
gmt | goto | head | html | i | id | if |
implements | import | in | instanceof | int | interface | into |
is | it | java | javascript | label | lang | language |
link | local | long | n | native | new | no |
not | obj | object | of | on | or | org |
package | page | param | pega | pegarules | pegasystems | primary |
private | property | protected | public | return | rule | rules |
s | script | short | static | strictfp | string | such |
super | switch | synchronized | t | table | tbody | td |
tempplace holder |
textarea | that | the | their | then | there |
these | they | this | tr | transient | throw | throws |
title | to | try | true | util | void | volatile |
was | wfe | while | will | with | y | yes |
For a complete description of Lucene search syntax, see: http://lucene.apache.org/java/2_3_2/queryparsersyntax.html
Lucene, pulse | |
Developer portal — Find tool |