|
|
|
A service consists of hardware, software, or other resources that users can request from the catalog. You create a service to group one or more service option groups together as a single service that users can request.
To add a new service
The Services page appears. It displays the folders containing services, organized hierarchically according to category.
Note: To add a service at the service provider (top) level, click the plus sign without expanding the tree.
The Folder Details dialog appears.
The Folder Details dialog is set for a new service (rather than a new folder).
Your specifications are recorded.
The Set Permissions dialog appears.
The dialog closes. Each role receives the access rights that you specified to the new service.
The service is saved.
You have added the service to the catalog. Define the service so that users can subscribe to the service or request it.
When you add a new service, the Folder Details dialog for a new service appears. You complete these fields as part of creating the service.
Adding a new folder is a related but unique task that displays a similar dialog, the Folder Details dialog for a new folder.
The following fields on the Folder Details dialog for a new service require explanation:
Displays the date the service was created. This field is read-only.
Note: The date and time shown are based on the time zone on the Service View server. The same is true for the date fields that follow.
Specifies the date when catalog users can request or subscribe to the service.
The dates and times that you enter in this field and the Date Unavailable field affect the availability of the service to catalog users.
Specifies the date when catalog users can no longer request or subscribe to the service.
Specifies the cancellation date for all accounts with subscriptions to this service and all requests for this service. On this date, the applicable subscription and request statuses are set to Canceled status.
Specifies the number of times an account or user can subscribe to or request the service.
Select one of the following:
Specifies the approval process to use for the service when a user requests it.
Note: This Approval Process setting does not apply to subscriptions.
Select one of the following:
Uses the following to determine whether the request for a service requires further approval:
If the authorization level of the user is less than the approval level of the service, the request requires further approval. In that case, the Catalog system does the following:
This process repeats until the authorization level of the approver is equal to or higher than the approval level for the service.
Specifies that the Catalog system does the following:
Note: Requests pending action can also be assigned to a group instead of an individual user. All users belonging to the assigned group see that request in their Requests Pending Action queues.
Approves the service automatically.
In policy driven request management, you specify conditions in policies, based on the attributes of service options, services, requested items, users, and so forth. If a policy is active and a submitted request meets the condition in the policy, the following occurs: The users (assignees) named in the policy receive a request pending action to approve, reject, or fulfill a service option, service, or request. If a policy does not apply to a request, the Catalog system uses the approval process specified for the business unit in which the request was created: This setting is typically the workflow driven approval process.
Specifies the approver Authorization Level required for the service: Level 0, Level 10, Level 20, and so forth. Specify these values at your discretion, relative to the policies and needs of your organization.
Specify these values logically and consistently to help ensure proper approval operations in your organization.
Note: This setting applies only if you specify System approval process in the Approval Process field.
Specifies the status of the request items in the service once the service is approved, one of the following:
Using Pending Fulfillment enables you to specify workflow processes that assign any additional tasks to fulfill the request, if necessary.
Note: This setting applies only if you specify System approval process or No approval process in the Approval Process field.
Specifies the version number of the service.
Enter the value in the format of major.minor.
Specifies a value of 1000 or greater.
Note: The values from 0 to 999 are reserved.
(Optional) Specifies any number.
Specifies the text value to represent the product code, subscription code, SKU # or any other applicable value.
Arranges the service option groups to appear to the user according to the category you select.
Categories include Name, Selection Type, Code, Date Created, and None. You can also select the category named Custom - use Sort Number. This option uses the Sort Number field in the service option group details.
Sorts the service according to the value you specify.
Note: This field applies only when the parent folder uses a value of Custom - use Sort Number in the Sort By field.
Assigns an image to a service.
Click Browse to select the image from the %USM_HOME%\FileStore\images\offerings folder.
Important! The folder name FileStore is case sensitive. Therefore, use the correct case in path names and all other programmatic references.
Note: For information about setting up the filestore, see the Implementation Guide.
The recommended size for an image is no larger than 48 x 48 pixels. However, the size of an image for a featured service is fixed at 32 x 32 pixels. Consequently, the image is reduced or enlarged to 32 x 32 pixels, regardless of its original size.
Therefore, if you make this service a featured service, verify that the image is legible when viewed at 32 x 32 pixels. Also, if you add images to several services in the same folder, verify that the sizes of the images are compatible. Verify that the images blend together to form a balanced layout that aligns with the Featured Item header.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |