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
Appendix C: XML tag reference
For this XML tag | Insert this value |
---|---|
<configurations> |
Define one or more <configuration></configuration> sections |
<configuration name="default">
</configuration>
|
Define all the necessary values to describe company customization values. The company name that you configure should match the default company name that is in the end user operator record. |
<companyDisplayNameKey>
</companyDisplayNameKey >
|
company_name is defined in ...\resources\client\en\Custom.properties Custom.properties Example:company_name = XYZ Example: <companyDisplayNameKey>company_name </companyDisplayNameKey> |
<resources></resources>
|
Define one or more <resource></resource> sections within this parameter |
<resource></resource>
|
panel.swf should be in this folder: Example:
Example: |
<styles></styles>
|
Define one or more <style><style> sections. |
<style></style>
|
styles.css should be in this folder ...\secure\configuration\default \
Example: styles.xml contains your custom display settings. Example: |
<launchersGroup> |
Define the launchers that will appear on each landing page. |
<launchers
displayOn="landingpage"
showIconOnly="false" showButtons="true">
horizontalAlign="left"
</launchers> |
Identify the third party launchers that will appear on the Dashboard and other landing pages. displayOn=DASHBOARD|SERVICE|SUPPORT showIconOnly= "true"|"false" showButtons="true"|"false" horizontalAlign="left|right" |
<launcher
displayOrder="n"
launcherId="id"
target="_blank|_self"
showLogoBox="true"
showLogoDropShadow="true"> |
You can show the logo as an icon and apply a drop shadow to the icon.
showLogoBox="true"|"false" showLogoDropShadow="true"|"false" |
<logo></logo> |
Your launcher logo file should be in this folder: ...\secure\configuration\default\applications The optimum size is 83x83px and the resolution should be 72 dpi. Example:...\secure\configuration\default\applications\abc.png The file format must be .png, .gif, or .jpg Example:<logo>abc.png</logo> |
<titleKey></titleKey> |
titleKey value from the Custom.properties file. Example:<titleKey>launcherName</titleKey> The inserted ID value cannot contain blanks. Use underscore characters as separators if necessary. The display value can contain blank characters. Custom.properties Example: Id Value Display Value launcherName = XYZ Company |
|
descriptionKey value from the Custom.properties file. Example:<descriptionKey>launcherDesc</descriptionKey> The inserted ID value cannot contain blanks. Use underscore characters as separators if necessary. The display value can contain blank characters. Custom.properties Example: Id Value Display Value launcherDesc = The XYZ Company gives you information about XYZ widgets! |
|
Specify the type of third party link:
The link type value must be upper case. Example:<launcherType>MEDIA</launcherType> |
|
Optional: Define one or more individual fields to appear in a popup window. |
|
Define a field that will appear in a pop-up window. Field ID is a unique user-defined value for each field. Example:<field fieldId="GetName"> |
|
labelKey value from the Custom.properties file. Typically, this is an informational label or text string that might precede a text box or just communicate information. Example:<labelKey>textLabel</labelKey> Custom.properties Example: Id Value Display Value textLabel = Select One: or textLabel = You are about to open a new window. |
|
Type of field. Choose one:
Note: Make sure you type these values in upper case. Examples: <type>TEXT</type> <type>TEXTAREA</type> <type>DROPDOWN</type> <type>HIDDEN</type> |
<defaultValue> |
Specify a constant value to display, such as a list item or other value that you want to pre-populate with static content. Examples: |
<options> </options> |
Insert individual <option></option> values to define values for a dropdown list. |
<option></option> |
For each <option></option> tag set, insert <labelKey></labelKey> and <value></value> tags and related values. Example: <option> <labelKey></labelKey> <value></value> </option> |
<labelKey></labelKey> |
labelKey value from the Custom.properties file. In an option list, specify the key name of a single list value that you want to display in the user interface. Example:<labelKey>dropdown_1</labelKey> Custom.properties Example: Id Value Display Value dropdown1 = Black dropdown2 = Red |
<value></value> |
This value can be the same as you defined in the Custom.properties file, or might be a different value to be passed to the third party application server. Example: <value>color</value> |
|
The action describes how data will be passed to the third party application. |
|
Insert the URL for the link in a CDATA tag.
Example:<![CDATA[www.google.com]]> Example:<link><![CDATA[http://www.XYZ.com]]></link> |
|
Specify the appropriate action:
Note If the Post request is to access a different domain (server URL), you must confirm that there is a cross-domain policy file configured at the root directory of the remote domain. The cross domain policy file grants access to the sender passing transactional data to that server. Example: Successful connection to a third-party application in a remote domain, like www.XYZ.com requires a crossdomain.xml file to exist at this location: www.XYZ.com/crossdomain.xml The crossdomain.xml file would contain a section like this: <cross-domain-policy>
<allow-access-from domain="*.ABC.com" secure="false"/>
</cross-domain-policy>
Examples: <method>GET</method> <method>POST</method> |