Setting up the My Stuff page

End users can view all items assigned to them on their My Stuff page in the end user console.  BMC Helix Digital Workplace administrators and BMC Helix Digital Workplace Catalog administrators configure the My Stuff view for end users. 

End users can view the following items on their My Stuff page:

Categories of items

Items displayed on the My Stuff page are organized by the following categories:

• Service health (predefined category)—Displays services followed by an end user, and service health items
• Asset groups (custom categories)—Displays completed service requests, and assets entitled to an end user

Service health 

All service health items is the predefined category available only if the Service Health feature is enabled in the Admin console. The available services have one or more actions associated with them, displayed in the Actions lists. The administrator creates and configures services and service actions. For details about how they are created and configured, see Setting up service health items.

The following image shows the predefined All service health items category:

For details about how to create service health items and associate service actions with them, see Setting up service health items.

Asset groups

Completed service requests with service actions associated with them, and assets and service requests entitled to an end user are displayed in categories under My items. The categories that are automatically generated based on asset groups to which service requests and assets belong. For details about how to create asset groups, see Managing asset groups.

In the following screenshot, Cloud services and Computer and mobile devices are two asset groups that display assets and service requests entitled to an end user:

Provisioned service requests and assets

The My Stuff page displays service requests and assets provisioned to end users. For example, if an end user requests a laptop, and if this request is completed, the laptop service request is displayed on the My Stuff page.

The following diagram shows an example of how provisioned service requests and assets are generated on the My Stuff page:

Britney, an end user, requests for a service that originates from BMC Helix Digital Workplace Catalog, and has service actions associated with it. The catalog administrator has added this service to an asset group. When a service request is processed and closed in the external system, it becomes available on the My Stuff page.

Britney can also see an asset entitled to her. The catalog administrator has added this asset to an asset group, and an administrator of the external system has entitled Britney to use it.

Displaying provisioned service requests on the My Stuff page

A service request is automatically displayed on the My Stuff page if all of the following conditions are met:

• The service request is built on a service from the enhanced catalog.
• The service request has been processed and has a status of Closed.
• At least one service action is associated with a service used by the service request.
• The Service Requests option is enabled in Application Settings > Asset Management in the Catalog console.
• The service used by the service request is associated with any asset group.

Removing provisioned service requests from the My Stuff page

A provisioned service request is automatically removed from the My Stuff page if a catalog administrator performs any of the following tasks:

• Deletes an asset group associated with the provisioned service request.
• Deletes all service actions from a service associated with the service request.
• Deletes a service associated with a provisioned service request.
• Designs a workflow mapped to a service action to remove a provisioned service request from the My Stuff page. For details on how to configure such a workflow, see Designing a workflow to remove a service request from the My Stuff page. 

Displaying assets on the My Stuff page

An asset is automatically displayed on the My Stuff page if all of the following conditions are met:

• The catalog administrator configures a connection with an external system. 
  To use assets from BMC Helix ITSM, the connection with the BMC Helix ITSM connector must be configured in Connector Management. For more details about configuring connectors, see Configuring service connectors.

• The catalog administrator enables the connection in Application Settings > Asset Management  > Asset Connectors. For more details about how to configure BMC Helix ITSM: Asset Management, see Configuring services and assets to be available on the My Stuff page. 

  To use assets from the external system, the Remedy connection must be enabled in Application Settings. For details about how to configure the connection for any connector, see Configuring service connectors.

• An administrator of a connected asset management system creates and entitles end users for using assets.
  To use assets from the BMC Helix ITSM connector system, the BMC Helix ITSMadministrator must entitle end users for using configuration items (CIs) in BMC Helix ITSM: Asset Management. For more details, see Creating and modifying CIs

• The catalog administrator creates an asset group on the Asset Groups tab, and adds an asset class to this asset group. The asset class includes assets that are entitled to an end user.

• The asset is not marked for deletion in BMC Helix CMDB. For more information, see  Deleting CIs in CMDB Explorer .

Removing assets from the My Stuff page

An asset is automatically removed from the My Stuff page if any of the following conditions are met:

• The catalog administrator deletes an asset group to which the asset is mapped.
• The administrator of an asset management system removes a user from the list of users entitled to use the asset.

Service actions

Service actions (also known as Day 2 actions) can be viewed and selected from the Actions list available for each provisioned service request, and can be available for assets.

Service actions provide an easy way for end users to interact with their service requests. For example, if an end user requests and receives a laptop, and later needs to add more RAM or HDD memory, the end user can find the laptop service request, and select Add more memory action available in the Actions list.

Service actions can be any of the following types:

• Predefined service actions are available by default if a requested service is built on a workflow that uses any actions from one of the following configured connectors:
  • Microsoft Office 365 connector
  • Microsoft Azure connector
  • AWS Marketplace connector
  • AWS Service Catalog connector
  • Flexera connector

The following example shows predefined service actions for a service request that uses Microsoft Azure connector:

• Custom service actions are added and configured by catalog administrators or internal service suppliers in BMC Helix Digital Workplace Catalog. For details about how to create service actions and associate them with enhanced services, see Managing service actions.

The following example shows custom service actions for a service request that uses AWS Service Catalog connector: