Unsupported content

 

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.

Creating a requestable offering definition

From the BMC Cloud Lifecycle Management Administration Console, you can create a requestable offering definition.

This topic includes the following sections:

To create a requestable offering definition

  1. From the BMC Cloud Lifecycle Management Administration Console, open the Service Catalog workspace.
  2. Select an existing Business Service (or create a new one).
  3. Select the Service Offering (or create a new one).
  4. Click Create the request definition.
  5. In the Requestable Offering Definition dialog box, complete the following fields:

    Field

    Description

    Title

    Enter a descriptive title for the requestable offering.

    Description

    Enter a detailed description of the requestable offering.

    Note

    Only 255 characters can be shown in the Request Entry console. Any text greater than 255 character is indicated by ellipsis points (...), although you cannot access this text in the Console.

    In addition, you can enter any value that can be read by a browser. For example, you can enter the URL of your company or the URL for a form on the web. The web page, form, or interpreted code appears in the Description field when requesters access the requestable service.
    For example, you could add the following JavaScript snippet:
    <a href="#" onClick="window.open('http:// www.bmc.com', 'win'); return false">

    Keywords

    Enter aliases (keywords) used to search for requestable offering in the My Cloud Services Console.
    Requesters can enter these keywords when they search for services in the My Cloud Services Console.

    Price

    Enter the actual price of this requestable service.

    Start Date

    Enter the date that this requestable offering goes online.
    After the requestable offering is approved and deployed, it becomes available online after the date you enter here.

    Change Policy

    Specify the type of Change Policy to be used. The options are

    • No Change Required — No change request is created as part of fulfillment.
    • Audit-Only Change — A change request is created that can be audited but not modified.
    • Pre-Authorized Change — A pre-authorized change request is created.
    • Change Approval Required — A change request that requires approval is created. Fulfillment activities cannot begin until the change request is approved.
      To delete the change policy, select No Change Required.

      The cloud fulfillment process uses the policy to determine whether a change request is created to fulfill the request.

    Type

    Select the advanced interface form that the user must complete for the requestable offering. Typically, you select Compute. If the requestable offering is part of an Amazon Elastic Compute Cloud (EC2), select EC2.

    Add-on

    Select Yes if you want contract line items created when the user requests this requestable offering.

    Image

    Specify which image appears to users in the My Cloud Services Console.

    Approval Type

    Specify the type of approval required for the service request:

    • None — No approval chain record is associated with the service request when it is submitted.
    • Manager — Enables you to specify how deep you want to go in the management approval chain. For example, if you use 1 (the system default), the chain extends only to the user's manager. If you enter 2, the next level in the management chain must approve the upgrade, and so on. The maximum number of approval levels is 5.
    • Person — Enables you to send the service request for approval to any user defined in the People form. Click Select to search for any user available in the People form.
    • Group — Enables you to send the service request for approval only to group members with Request Approver roles.
    • Custom — Enables you to use a custom approval chain (not one of the approval chains installed with the application).This custom approval chain definition must have a Selection Criteria that matches the requestable service.
  6. Click Next.
  7. Specify the category type that applies to the requestable offering (for example, Telecommunications Services > Conference Calling > Conference Call Setup).
  8. Associate one or more packages with the requestable offering. Note that at least one package needs to be associated with the requestable offering
    1. To associate a package, select it from the Available Packages table, and click Add.
      You can also drag and drop packages from the Available Packages table to the Associated Packages table.
      Packages that are related to the Company for this requestable offering are listed in the Available Packages table.
    2. To filter the packages listed in the Available Packages table, enter a word or string in the Search field, and press Enter.
  9. Click Finish.

To apply entitlement rules to global requestable offerings

By default, Service Request Management does not apply entitlement rules to global requestable offerings. However you can change the default setting in the Entitlement section of the the Application Administration Console.

To change this setting, you must be a member of one of the following permission groups:

  • SRM Administrator
  • AR System > Administrator
  1. Log on to the Application Administration Console.
  2. Click the Custom Configuration tab.
  3. Navigate to Service Request Management > Entitlement > Entitlement Management.
  4. Click Open.
    Entitlement Management is displayed.
  5. Next to Apply Entitlement Rules to Global SRDs, click Yes.
  6. Click Close and exit the Application Administration Console.

Related topics

Creating cloud services

Was this page helpful? Yes No Submitting... Thank you

Comments