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.
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 |
|
|
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 |
|
Invoke Rule Sets from triggers
Applies to User Roles:
System Administrator
If Process Designer is not implemented in Service Management, you must invoke a Rule Set from a SMA Service Management trigger, by adding the following API in the trigger's script:
lib.CaseExchange_RuleExecute.executeSingleRuleSet(record,oldrecord,RuleSetID)
The following table explains the meaning of each parameter in this API.
Parameter | Description |
---|---|
record | The new record. |
oldrecord | The old record. |
RuleSetID |
The ID of the Case Exchange Rule Set. For example, |
To add a trigger that invokes a Rule Set, follow these steps:
- Click Tailoring > Database Manager. The Database Manager page opens.
- Type triggers in the Table field, and then click Search. The Search Trigger Records page opens.
-
Complete the following fields:
Field Description Trigger Name The name of the trigger. Table Name The file to be monitored by this trigger. Trigger Type Select the specific activity to react to:
1 - Before Add - When adding a new record to this file, launch the application prior to committing the addition.
2 - After Add - When adding a new record to this file, launch the application after committing the addition.
3 - Before Update - When modifying a record in this file, launch the application prior to committing the change.
4 - After Update - When modifying a record in this file, launch the application after committing the change.
5 - Before Delete - When deleting a record in this file, launch the application prior to performing the deletion.
6 - After Delete - When deleting a record in this file, launch the application after performing the deletion.
Note: Only triggers of type 4 (After Update), and type 6 (After Delete) are supported by Cascade Updates.
Application The RAD application to be launch by this trigger. If you only intend to invoke a Rule Set by using this trigger, leave this field empty. Script Call the following API by using appropriate parameters:
lib.CaseExchange_RuleExecute.executeSingleRuleSet(record,oldrecord,RuleSetID)
- Click Add.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to docs.feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: