Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Management2017.11

Develop > Programming Guide > System language

System language

The System language (RAD) provides the ability for administrators to manipulate the ITSMA Service Management processes and workflows using a programming language with a syntax that is similar to the C programming language. Administrators and implementers use this language daily to apply Service Management to a specific purpose or enterprise. The key to Service Management’s remarkable flexibility can be found in the proper use of the system language.

The System language creates RAD applications that contain application panels (records) linked together in a logical flow. Each panel performs a specific function. When the function is complete, the application exits to another panel. The field value within the exit is a label name of another panel.

The parameter panel defines local variables passed to it by a calling application. In general, two kinds of local variables exist: those used within an application, and those used as exits. Normally, the exit variables are $normal (in the normal exit) and $error (in the error exit).

The first command panel, where execution begins, is always labeled start. Execution continues at a panel’s normal exit (or another exit depending on conditions). When that exit is defined as $normal, execution of the panel is complete. If an error is encountered, then the $error exit is taken.

Note You must have a RAD license to view and modify the RAD applications with the RAD editor.

Send Help Center feedback