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 |
|
- Service Request Catalog Customization
- Configuration files
- Working with manifest.xml
- Using the Migration Tool
- Service Request Catalog customization
- Service Manager configuration for Service Request Catalog
- Miscellaneous tasks
- Appendix A: Launcher Examples
- Appendix B: Service Catalog in Service Manager
- Appendix C: XML Tag Reference
- Appendix D: Styling the interface
- Appendix E: Fields available for advanced search
Working with the manifest file
This file contains information about the presentation of the Dashboard and other landing pages for your company. This file also points to other resources that contribute to the look and feel of your user interface, such as your company name, color palette, and other presentation styles.
The manifest.xml
file has basic sections for capturing this information.
<configuration name=""> <companyDisplayNameKey> <resources> <styles> <launchersGroup> <widgetsGroup> </configuration>
See the Appendix C: XML tag reference for more information about configuring the individual tags in each section.
Use the validator tool for manifest.xml
Service Request Catalog comes with a prepackaged validation tool that you can use to help ensure that your manifest.xml
file is valid and usable. The validator tool can be found in the Service Request Catalog release .zip package. The vtool consists of the following two script files for Windows and Linux operating systems:
- validator.bat
- validator.sh
For example, you would enter the following command on a Windows system to use the validation tool:
validate.bat -c "<path>"
Note The <path> placeholder tag represents the file system path where you have the manifest.xml
file.
After running this command, you will receive the following message if your manifest.xml
file is valid:
"manifest.xml is valid!"
If your manifest file
is not valid, you will receive an error message. The following table demonstrates some of the error messages you may receive:
Error: Cannot read manifest file: <path> | Description |
---|---|
org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: 'abc' is not a valid value for 'integer'. | A string value is present in some elements that requires an in integer value. |
org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element 'configurations' is not complete. One of '{configuration}' is expected. | The <configurations> parent node must contain at least one <configuration> child node. |
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'resources'. One of '{styles, widgetsGroup, launchersGroup}' is expected. | The <resources> element can contain only one of each of the following: <styles>, <widgetsGroup>, <launchersGroup> |
org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'displayOn' must appear on element 'launchers'. | The displayOn attribute is not present in the <launchers> element. |
org.xml.sax.SAXParseException: cvc-enumeration-valid: Value 'CHOICE' is not facet-valid with respect to enumeration '[TEXT, TEXTAREA, DROPDOWN, HIDDEN]'. It must be a value from the enumeration. | Type of fields in the <launcher> must be a value from the enumeration [TEXT, TEXTAREA, DROPDOWN, HIDDEN]. |