When you add or edit a service, you complete the fields on the Details tab for the service.
The following fields on the Details tab for a service require explanation.
Assigns an image to a service.
Click the existing image to select the new 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. So, 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.
(read-only) Specifies the object ID of the service.
At times, you specify object IDs explicitly, for example, as part of importing or exporting objects using ixutil or content packs.
Specify the name and description of the service for catalog users. You can optionally localize these fields for use in a multilingual catalog.
Specifies the text value to represent the product code, subscription code, SKU number, or any other applicable value.
Specifies an external URL for more information about the service. For example, a service for a new laptop can include the URL to the manufacturer specifications page for the laptop.
The dates and times that you view and specify are based on the time zone on the CA Service Catalog server, which can be different from your local time.
The dates that you enter in the Available On, Unavailable After, and Canceled After fields affect the availability of the service to catalog users. The changes that you make to these fields take effect immediately.
The following date fields require further explanation:
Specifies the date when catalog users can no longer request or subscribe to the service.
Specifies the cancelation date for all requests for this service and all accounts with subscriptions to this service.
On this date, these subscriptions and requests are canceled. Requests and subscriptions that are in progress are canceled immediately.
Specifies the business hours for the service. The business hours are the regularly scheduled days and times of service, for example, Monday-Friday, 9:00 am to 5:00 pm. Business hours apply only when you use request SLAs to help measure the availability of a service.
Click the link to search for an existing business hour specification and attach it to this service.
Specifies the outage calendar for the service. The outage calendar specifies days, dates, and times when the service is not available, for example, weekends, holidays, and one-time outages. Outage calendars apply only when you use request SLAs to help measure the availability of a service.
Click the link to search for an existing outage calendar and attach it to this service.
Specifies whether users request the service by using the one-click submit method or by using a shopping cart.
Lets users request the service, using one click, without a shopping cart. This method submits a stand-alone request for the service.
The one-click submit method is appropriate for the internal business and personnel services of an organization that are not related to shopping. Examples include services for onboarding new employees and for setting up or accessing virtual computers or file shares.
When you use the one-click submit method for a service, users cannot include it in the same request as other services.
Lets users request this service by adding it to a shopping cart. The cart can include multiple services. The user finishes shopping, verifies the cart, and submits it. This method is appropriate for services that are related to internet shopping (e-commerce), typically procurement requests. Examples include requests for new hardware or software.
A catalog user who has added services to a shopping cart but has not submitted the cart can request a service configured for one-click submit. The request for the one-click submit service is submitted immediately as a separate stand-alone request, and the shopping cart is not affected.
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 options:
Uses the following options 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 performs the following tasks:
This process repeats until the authorization level of the approver is equal to or higher than the approval level for the service.
Approves the service automatically.
Uses a CA Process Automation process to determine the approval process.
The process includes the business logic to determine the approver and the number of approval levels. CA Service Catalog provides sample processes, including default ones for a single level of manager approval.
For any service, if you use this approval process with a CA Process Automation process, you can optionally use policies. In that case, the approval process proceeds the same as with Policy driven approval process, except as follows:
Verify that the rules and actions are enabled for the option that you specify.
Uses policies to determine the approval process for requests. 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, then 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.
Policy driven approval and system approval use a few common terms. For example, in both methods, the level of approval refers to the authority of an approver in numeric terms: the higher the number, the greater the authority of the approver. However, in policy driven approval, the administrator assigns each approver and authority level uniquely, with no relation to system approval.
If a policy does not apply to a request, the Catalog system uses the approval flow defined in the workflow driven approval process. For example, you are using the predefined workflow approval process and no predefined sample policy applies to a request pending action. In that case, the Catalog system assigns the request pending action to the manager of the Requested For user. If the user has no manager, then the system assigns the request pending action to the Default User for Request Actions This user is specified in the Catalog Configuration.
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 verify proper approval operations in your organization.
Note: This setting applies only if you specify System approval process or Workflow driven approval process in the Approval Process field.
Specifies the number of times an account or user can subscribe to or request the service.
Select one of the following options:
Specifies the status of the request items in the service once the service is approved. Select one of the following options:
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.
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.
|
Copyright © 2013 CA.
All rights reserved.
|
|