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 |
|
Version control best practice
Create an operator record for each developer
Each developer should have their own operator record to log in to Service Manager rather than using the default System Administrator operator record. This helps to track code changes, because the value of the sysmoduser field of the applicatios object is set as the currently logged-in user.
Streamline the code repository versions
Prior to any development, export the Service Manager OOB database as the initial repository for future comparison and analysis. Then, export your organization’s current, customized database as the second-version repository.
Note When you upgrade Service Manager to a later version and resolve all conflicts, you must export the complete upgraded database again as the new code repository.
Turn off this function when it is not needed
The source version control function decreases system performance. Therefore, you should comment out the source version control configuration lines in the sm.ini
file when it is not needed.
Synchronize number/counters records after merging updated code to another environment
When you merge updated code to another environment, sometimes the maximum ID number in number/counters records may not synchronize with the related records. Run the following script to synchronize data:
run ScriptLibrary lib.BaseUtil.function synchronizeCountersAndNumbers()
Related concepts
Implementing version control for your tailoring
Related tasks
Related references