Cisco Cisco Prime Service Catalog 10.0 Technical References

Page of 216
 
1-54
Cisco Prime Service Catalog 10.0 Configuration Guide
OL-31034-01
Chapter 1      Organization Design 
Roles
Such an environment can be established via the use of Permissions associated with Service Designer 
components. You could set up a custom role for each development group. (Members may be assigned 
either directly or indirectly, via membership in a service team or group.) In Service Designer that role is 
able to:
  •
Design services … in this service group (service groups containing services maintained by the team)
  •
Order services in this service group
  •
View services in possibly related services groups, or groups that might have interesting techniques 
for them to see
  •
Design forms in their own form groups
  •
View forms in the reserved group
  •
View forms in any other (common?) groups that they might need to include in their services
Rather than giving the custom role a preexisting Service Designer role, it would be preferable to grant 
appropriate Service Designer capabilities to the role. This option may be more work to set up, but gives 
you more flexibility. One thing to be careful about is in granting the group the right to import services. 
You could import a service and overwrite components (dictionaries or forms) that you do not normally 
have the ability to modify. The Import Service option does not check object-level permissions, it just 
overwrites (or creates) everything.
Support for Web Services
In addition to users being able to submit requisitions via My Services, Service Catalog provides the 
ability for external systems to submit requisitions via a web service request, using the Requisition API 
(RAPI). Such requests, bypassing My Services or the Service Catalog module, would never have a 
service form appear in the ordering moment. Consequently, their design would need to differ from that 
of a corresponding service that is ordered interactively. For example, no rules or Java Script functions 
could provide default values; and multi option fields, such as check boxes or drop-down lists, could not 
be used.
As a result of those limitations, designers sometimes choose to create a set of parallel services that can 
only be ordered via RAPI. Such services should never appear in the Service Catalog of nonadministrative 
users. Instead, ordering permissions should be granted only to administrative users. The RAPI service is 
always ordered by such a user who has been assigned the critical capability to “Order my services for 
others”, with the “other” specified as the customer for the request.