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 |
|
How to enable change collision detection
To enable change collision detection, you must add a business rule to the After change section of the Change process. (For more information, see here.) If you want to also detect change collisions affecting the same device, you must also add a business rule to the Before adding relationship section of the Change process. (For more information, see here.)
The business rule added to the Before adding relationship section of the Change process, checks collisions between change records with matching times when there is a change to their involved device .
For example, assume two change records have matching times but different involved devices. At a later date, if one of the change records is modified so that they have the same involved device, the business rule generates a collision alert. However, where there is the appropriate business rule in the After change section, but not in the Before adding relationship section, change collision is only detected when start or end times are modified.
Change collision detection business rule
This feature uses the Validate no collisions business rule template. There are the following versions:
-
In the After change section of the Change process
-
In the Before adding relationship section of the Change process
After adding the rule, you should edit it as follows:
Field | Value |
---|---|
expression |
Caution It is possible to create a simple rule using this template without the "If...Then" option and the expression parameter. However, such a rule would run every time a change record is saved (if defined in After change), and on every added association (if defined in Before adding relationship), likely having a materially adverse effect on performance. It is therefore recommended that you configure this rule template by always including an expression parameter. |
start time |
Select a suitable start time field. This is the start time of the current change being worked on that change collision detection checks. For example, Scheduled start. |
end time | Select a suitable start time field. This is the end time of the current change being worked on that change collision detection checks. For example, Scheduled end. |
changes |
Note: This field displays only for the rule in the After change section of the Change process. Select:
|
filters |
Select to filter the change records that the business rule is applied to. You may filter using fields of the following types only
For example, you might choose category, or change model, or owner. |
start time field end time field |
Select a suitable start time field and end time field. The business rule compares the start time to end time (as determined above) of the current change record being worked on, with the start time field to the end time field of other active changes. For example, you might have the following settings:
The business rule then detects change collisions between the Scheduled start and Scheduled end of the current record being worked on, with the Scheduled DT start and Scheduled DT end for all other active changes. |
How to add a change collision detection rule to the After change section of the Change process
-
From the Main menu, select Administration > Configuration > Records.
-
In the drop-down at the top of the page, select the Change record type.
-
Select the Processes and Rules tab.
-
In the left pane, select Change at the top of the tree.
-
In the main panel, in the After change section:
-
Click Add.
-
Click “If…Then” rule.
-
Select the Validate no collisions rule template, and click OK.
-
-
Edit the newly created rule as required, and save your changes. For more information, see Change collision detection business rule.
How to add a change collision detection rule to the Before adding relationship section of the Change process
-
From the Main menu, select Administration > Configuration > Records.
-
In the drop-down at the top of the page, select the Change record type.
-
Select the Processes and Rules tab.
-
In the left pane, select Change at the top of the tree.
-
In the main panel, in the Before adding relationship section:
-
Click Add.
-
Click “If…Then” rule.
-
Select the Validate no collisions rule template, and click OK.
-
-
Edit the newly created rule as required, and save your changes. For more information, see Change collision detection business rule.