|
|
|
The catalog supports services that contain multiple service option groups. In this starter implementation, however, most services contain one associated service option group. As the catalog designer, you decide to use either one or multiple service option groups per service. In both cases, we recommend that you organize related service option groups in services logically and intuitively.
Focus on the user when designing services and service option groups. A common flaw in catalog design is placing service option groups in a nonintuitive service or folder. When service option groups in a service or folder are unrelated, users have difficulty finding the services they want. For example, consider a service option group for a network design program. You could place it in a service or folder named Development Tools. However, such a service option group fits better in a service or folder named Miscellaneous Software. A network administrator is more likely to view the latter folder first for this program.
The catalog provides a search tool that can be helpful. This tool supplements thoughtful design, but does not replace it.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |