Customizing › Custom Branding › Page Header and Footer Elements

Page Header and Footer Elements

The following window identifies the various elements of the product user interface that can be customized.

Note: Your company’s browser window may look different than the following one.

Each element identified in the table below can be customized by replacing or editing the corresponding file.

Note: For the Text elements, the file is shown in the folder location for an English system (icusen). For other languages, the file location will be different.

How to Customize XSL, XML, JavaScript, and Image Files

CA Service Catalog includes several hundred XSL, XML, JavaScript, and image files. Together, they are used to form every page and every page element in the product. Each file represents one page or a part of a page, such as a dialog, menu option, form field control, message, or picture.

Every file is named intuitively to illustrate its function. You can optionally customize any of these files to meet your requirements.

To customize XSL, XML, JavaScript, and image files, follow this process:

1. Determine the specific page or part of a page that you want to customize.
2. Locate the file whose name matches the element you want to change. For example:
   • To modify the configuration information of any of the integrated products, locate the toolsconfig.xsl file.
   • To modify states of request lifecycle, locate the requestshared.xml file.
   • To modify the messages that appear when the connection for a new setting on the Administration, Configuration page is tested, locate the toolsconfig.js and toolsconfig.xsl files.
   • To modify the edit button of the Administration, Configuration page, locate the modify.gif and toolsconfig.xsl files.
   • To modify the request status list, locate the requeststatus.xml file, as described in How to Maintain the Request Status List.
   • To use a JavaScript function to customize a form, see the Administrator Guide.
3. Open the file, review it contents, and verify that it controls the element or behavior that you want to change.
4. Using the table at the end of these steps as a reference, copy the file from its original location to the custom location.
5. Modify the file to meet your requirements.
6. If you customized a JavaScript or image file, perform this step; otherwise, skip it.
   1. Copy the customized JavaScript file to the \FileStore\custom\explorer\scripts folder.
   2. Copy the customized images to the \FileStore\custom\images folder.
   3. Locate the XSL file in the custom location in which the JavaScript or image file is used.
   4. Update this XSL file to specify the new custom path name of the JavaScript or image file, by prepending "FileStore/" to the relative path of the JavaScript or image file, as shown in the following example:

         <script src="FileStore/custom/explorer/scripts/custom_form_example.js"></script>
      

      This action is required because the XSL file references the filestore location for the customized script files.

7. Clear the %USM_HOME%\view\translets folder: delete all files in this folder, but do not delete the folder itself.
8. Restart Service View.
9. Verify that the changes are working in CA Service Catalog as you intended.

In the following table, the parent folder is %USM_HOME%/view/webapps/usm. The filestore folder is %USM_HOME/filestore. The folder entries, such as /explorer and /custom/explorer, are sub-folders under the parent and filestore folders.

*The folder name icusen applies to English-language implementations only. If you are using a non-English implementation, your locale-specific folder name is different. In such cases, use your locale-specific folder name instead of icusen.