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 |
|
- Display application
- Displayscreen definitions
- Display application option definitions
- Restricting access to display options
- Selecting display options
- Calling an application
- Custom RAD
- Creating displayscreen records
- Displayoption Database Dictionary keys
- Displayevent Database Dictionary keys
- Access display records
- Create a displayscreen record
- Create a displayoption record
- Define display conditions
- Enable the Merge Conflicted Updates function for customized user operations
Enable the Merge Conflicted Updates function for customized user operations
System Administrator |
The Merge Conflicted Updates feature is out-of-box for Service Manager 9.60 default user operations. However, to apply the Merge Conflicted Updates function to a record with customized operations, you need to tailor your customized operations first.
The following example describes how to enable the Merge Conflicted Updates function for all operations on Service Desk. In this example, you need to:
- Enable manual merge operation for Service Desk.
- Enable auto merge operation for all operations.
Task 1: Add a display option for the Merge Conflicted Updates function
- Click Tailoring > Tailoring Tools > Display Options.
-
As listed in the table below, fill in the required fields to add the display option:
Field Value Screen ID The display screen you are using to display Service Desk records. For example, cc.edit.incident. Unique ID cc.edit.incident_merge Action merge GUI option Unused number under the display screen. For example, 5. Text option Unused number under the display screen. For example, 5. Bank 1 Balloon Help Merge Default Label Merge Text Alternative Merge Condition updatestatus($L.file)=$G.RC.MODIFIED and gui() and $L.mode~#"add" - Click Add.
Task 2: Add process call in the State record of a Service Desk Object.
- Click Tailoring > Document Engine > States.
- Search for the state that you use to view a Service Desk record. For example, sm.view.
-
As listed in the table below, add the values to the last line of the Non-base methods table:
Column Value Display Action merge Process Name record.update.conflicts Condition true - Click Save.
By completing the first two tasks, you have enabled the manual merge function for Service Desk. If the record being updated has been modified since being read, the Merge button appears on the option toolbar.
Task 3: Enable auto merge operation for all operations.
- Click Tailoring > Tailoring Tools > Display Screens.
- Search for the sd.view record.
-
On the Javascript tab, append the following code in the text box:
var mergeResult = lib.recordUpdateConflicts.autoMerge();
- Click Save.
By completing the third task, you enable the auto merge function for all operations. If there are conflicted updates of the same field, the auto merge process does not merge this record. Instead, you must perform a manual merge operation.