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. Click here to view the documentation for the current version.

3.2.00 enhancements

This section provides information about what is new or changed in this space, including urgent issues, documentation updates, service packs, and patches.

Tip

To be notified of changes to this space, place a watch on this page .

BMC MyIT Service Broker 3.2 is the digital app store for the enterprise. For an overview of the application menus, watch the following video. (3:17).

https://youtu.be/keeX0EhuDmA

Review the following enhancements with this release.

Service price and cost adjustments updates

The Service Options > Cost & Quantity module merges the capability to set quantity ranges for services and bundles.

Pricing and cost adjustments enhancements:

  • Set the one-time or recurring price of a service in the default currency. The system administrator sets the default currency at the tenant level.
  • Add cost adjustments to offset costs, such as administrative charges and vendor rebates.
  • Save cost adjustment profiles for use when editing other items.

New request quantity features

Enable the user to request multiple quantities of a service:

  • When editing a service, the option for the user to adjust the request quantity is enabled by default. You can set the minimum and maximum quantity of the service that the user can request.
  • When you disable the option for the user to adjust the request quantity, the default service quantity is set at 1 request unit.

Enable the user to request multiple quantities of a bundle, and the option to enable the user to request multiple quantities of each service within the bundle:

  • When editing a bundle, you can set the quantity range limit for the overall bundle. The option for the user to adjust the request quantity of each individual service is disabled by default.
  • When you enable the option for the user to adjust the request quantity at the service level, then you can set the minimum and maximum quantity that the user can request of each of the services in the bundle.

Service bundling enhancements

This release includes the following enhancements to bundling services:

  • While viewing the Services > My Services tab, click Create New and select either a service or a bundle.
  • Bundled services can be provisioned either by the workflows of each individual service, or by a custom workflow that you define. Drag and drop the services to reorder the sequence in which the services will be fulfilled.
  • In a bundle, you can allow some services to be optional, so the user can choose whether to request them or not. When optional services are included in a bundle, the bundle will be fulfilled by the individual services workflows by default.
  • The bundle cost defaults to calculate the total of all bundled services. You can toggle this setting off to set a bundle cost.

Questionnaire enhancements

This release includes a completely redesigned question form builder:

  • When inserting Process Questions that feed into a fulfillment workflow, you can select from the following form element types:

    Text inputUser-selectableMultiple selection
    Text FieldDropdownCheckboxes
    Text AreaRadio ButtonsMultiselect Dropdown
    Password Field  
  • When entering text input fields, you can apply field validation based on character limit or regular expression. Sample regular expressions are supplied as tests for email address, phone number, web URL, IP address, and cost center.
  • When a regular expression is entered for use in validating user input, a formatting hint is displayed in the question builder to show the expected input. You can edit the formatting hint
  • When adding questions with user-selected answers, you can add conditions for each answer, and link future questions to be shown based on the user's choice.
  • You can assign default values for questions, set the question as read-only, and hide questions in the questionnaire that is presented to users.
  • You can add file upload questions to enable users to submit files when requesting a service. The ability to receive files must exist in the integrated system, for example, BMC Service Request Management supports file uploads.

Service entitlement enhancements

This release includes the following changes to entitling users and groups to services:

  • You can toggle Enable full catalog view to on to allow all users to view and request all services in the catalog.
  • You can restrict some services from being available to users who are not entitled to them even when Enable full catalog view is toggled on.

On-premises installation and upgrading enhancements

Full instructions are provided to install a fresh copy of BMC MyIT Service Broker 3.2, or for you to upgrade from BMC MyIT Service Broker 3.1 in-place.

  • The installation worksheet details each of the parameters in the options.txt file used by the silent installer, in response to customer feedback.
  • Post installation configuration instructions are provided to set up the application database with sample users, and to synchronize with BMC Remedy IT System users.

For installation instructions, see Installing.

For upgrading instructions, see Upgrading.

Service connector enhancements

This release adds the following service connectors to integrate with existing systems:

  • Microsoft Active Directory
  • BMC Atrium Orchestrator
  • Citrix XenMobile
  • BMC HR Case Management

For more information, see Installed service connectors.

Transfer services between service catalog systems

This release adds the following export and import feature:

  • You can export services from one BMC MyIT Service Broker system as a zip archive, and import the zip archive to create new services. The zip archive contains the catalog profiles, workflows, questions, and other metadata for all versions of the services.

BMC Service Request Management import enhancements

  • When importing service request definitions (SRD) into the service catalog, workflows and questionnaires are generated automatically. Most question types are supported, even fields with query qualification and action triggers.
  • After importing an SRD, if you choose to update any details about the SRD in BMC Service Request Management, you can import the service again to replace the existing service, even if you change the name.
  • Generated workflows include by default the feature to trigger an action and then wait for a response from BMC Service Request Management. For more information, see Waiting for a response.
  • Generated workflows cannot be edited directly. However, you can include generated workflows in custom workflows by combining the Build Input Set and the Call Activity. For more information, see Passing information to an activity and Calling external workflows.

BMC CMDB enhancements

  • Automatic creation of service offering (SO) and requestable offering (RO).
  • When importing an SRD with an existing BMC CMDB association, the service is mapped to the existing service offering.

Information

Context-sensitive embedded help available

Learn to use the features of BMC MyIT Service Broker with guidance from the context-senstive help embedded into the application.

To access the in-app help at any time, click the help icon in the header.

Get started today

Contact your BMC account representative to realize the benefits of BMC MyIT Service Broker at the core of your digital enterprise transformation.

 

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

Comments

  1. Sanket Mhatre

    Hi,

    Does Quantity field creates multiple requests; or how it can be used in the use case.? . For example , if associates required 2 laptops and selected quantity field as 2.. then do we need to use quantity field in some workflows to leverage or to use it as some variable.

    Thanks,

    Sanket

    Oct 21, 2016 05:52
    1. Tony Chung

      Hi Sanket Mhatre. Thanks for asking! The quantity is a value that is passed into the workflow using a property of the service broker context. For a list of all the supported properties of the service broker context, see: Capturing user request information.

       

      As only one request with a quantity value is submitted, your fulfillment system would need to support a quantity value passed as a parameter.

      To meet your use case, if associates submitted an order for 2 laptops, the workflow would send the quantity of 2 to the fulfillment system. The fulfillment system would have to interpret this value as a quantity and process the order accordingly.

      Oct 21, 2016 10:29