This documentation applies to the 8.1 version of Service Request Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring navigational categories

This section discusses configuring navigational categories.

The following topics are provided:

You define navigational categories to organize your SRDs. You must specify a top-level (Category 1) navigational category when creating an SRD, and you can optionally specify sub-categories (Category 2 and Category 3). The SRD is displayed under the selected category on the Browse page of the Request Entry console.

Notes

  • You must have the SRM Administrator permission to create navigational categories.
  • Navigational categories do not appear in the Request Entry console until they are associated with an SRD.
  • The Max Entries Returned By GetList server setting limits the number of SRDs and navigational categories displayed in the Request Entry console. Make sure that your administrator has configured this setting to accommodate the SRDs and navigational categories that you create. For example, if Max Entries Returned By GetList is set to 10, then only a total of 10 SRDs and navigational categories will display, even if more SRDs and categories are available. For more information, see Setting administrative options (BMC Remedy Action Request System documentation).

You define the categories in the Category Management form. This form is used as a repository to store the categorizations that differentiate the catalog offerings, including graphics. You can create generic categories that globally apply to all organizations (for example, Hardware/Computers) or categories unique to specific companies. For more information, see Defining global navigational categories and Defining company navigational categories.

When you define categories for one company, the appropriate categories visible only for that company. You can create three levels of categorizations for a specific company (for example, Installation > Desktop > Windows, or Change > Application > Password).

The company and categories enforce the uniqueness of the categorization, which means that only one unique combination of categories is allowed for each company and each locale.

Define global categories first, followed by company-specific categories, and then sort. Follow this sequence because you move company navigational categories up and down the navigation tree relative to the global categories. After you specify the sequence of the global categories, they are fixed and do not change when you start working on your company categories. After you establish the global categories, you move the company categories around them, above or below a global category.

The system prevents you from creating duplicate Category 1 records. You can, however, create Category 2 and Category 3 records that have the same name. For example, you can create two Category 3 records called Password Reset because the two different contexts in the Request Entry console determine its particular use.

Business Systems (Global Category 1)
	iTime (Category 2)
		Password Reset (Category 3)
Network (Calbro Category 1)
	NT Authentication (Category 2)
		Password Reset (Category 3)

As a result, users should not be confused by seeing Password Reset in two different locations in the Request Entry console.

Some SRD categories are preconfigured by default with their own images. You can relate a different image with these categories. In addition, when you configure your own navigational categories for your organization, you can assign customized images to them, based on your organization. (For more information, see Configuring service request images.)

After you define the navigational categories, their values appear in the following areas:

  • Service Request Definition form
  • Defined Locales form (click Other Locales on the Service Request Definition form)
  • SRD Qualification for Entitlement form
  • Approval Mappings

Recommendations

When defining navigational categories, consider the following recommendations:

  • Create a spreadsheet with the items you support on the left side (for example, Hardware, Software, Networks, and so on) and the services you provide on the top row (for example, Repaired, Replaced, Trained, and so on). Each spreadsheet cell represents a category and service pair (for example, Hardware/Repaired). Determine which pairs apply to your organization, and you can map your old tree to this new structure.
  • Follow this sequence of steps:
    1. Define global navigational categories 
      To avoid confusion in a multi-tenancy environment, create your most general categories as global. When you have finished the overall general structure of your Category 1, 2, and 3 records, you can create more particular categories for your company. Also, if guest users must be able to access navigational categories, create those categories as global.
    2. Define company navigational categories
    3. Sort navigational categories
  • Define only a manageable number of SRDs and navigational categories. Increasing the number of navigational categories to users can slow the performance of search operations in the Request Entry console.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. George Payne

    So, I understand that users should not be confused by finding "Password Reset" under both "iTime" and "NT Authentication", and I think they WILL be confused when they find it TWICE under "iTime" as it shows up in the figure above

    Jul 30, 2014 09:55
    1. Catherine Siderine

      Hi George,

      Thanks for your comment. I have updated the example to remove the extra "Password Reset" category.

      Regards,

      Cathy

      Jul 30, 2014 03:41