Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Registered events
Each event has a record in the eventregister table. Each event record includes a unique event code and a sequence number. A single event can start a series of applications. Each event record also contains initialization statements, mapping information and instructions for calling the Service Manager application. Registration is necessary for all input events that external applications process.
Example
Records in the eventregister table contain unique identification codes. The pmo code identifies opening an incident. When a pmo event occurs, Event Services calls the axces.apm application if the condition is true. The event parameters are passed by name and value. The Map Name identifies the event map to use when mapping the information into Service Manager tables.
The event registration record contains expression statements that create different queries, depending on the source of data. For example:$ax.query.passed=nullsub("flag=true and network.name=\""+2 in $axces.fields+"\"", "false")
if (index("axmail", evuser in $axces)>0) then ($ax.query.passed=nullsub("flag=true and logical.name=\""+1 in $axces.fields+"\"", "false"))
The query uses network.name to select open incidents for update. The SCAuto mail incident event uses logical.name.
The pmo event registration record instructs Event Services to:
- Select a record from the probsummary file (based on the query in $ax.query.passed).
- Map data from the eventin record ($axces) based on the incident open (evmap in $axces.register) map record.
- Open an incident.
In most standard Event Services input applications, the first two parameters passed are the event record and the name of the event map. An exception in standard Service Manager SCAuto applications is e-mail, which passes the mail record and the delimiter character.
Related topics
Event Services
Generating email messages
Input events
Mapping events
