Restricting services and bundles for end users
As a catalog administrator, you can prevent end users from requesting certain catalog services and bundles by setting them to unrequestable. You can also use this functionality when a service or a bundle is undergoing changes and you plan to make it available at a future time.
You can restrict on-behalf-of entitlements for specific catalog services like resetting passwords, allowing only requestors to submit such requests themselves.
Required license
To set a service or bundle to unrequestable
- In BMC Helix Digital Workplace Catalog, open a service for editing (see Adding-and-updating-services).
- Click Version Options, and select Unrequestable in the Service Options panel.
When a service or bundle is set to Unrequestable in BMC Helix Digital Workplace Catalog, it cannot be requested in the end user console, and the Add to Cart and Request Now buttons are not displayed in the details for that service.
The following message is displayed when an end user opens an unavailable service:
The following message is displayed when an end user opens an unavailable bundle:
To filter unrequestable bundles and services
- Open the Service Management > Revision History.
- Click Filter, and select the Unrequestable status.
The list of unrequestable services and bundles is displayed.
Unrequestable services required in bundles
Setting a service to Unrequestable in BMC Helix Digital Workplace Catalog affects all published bundles that include this service as follows:
- If the service is set to Required in the bundle, the associated bundles become unavailable.
- If the service is not set to Required in the bundle, the associated bundle is available, but the unavailable service in the bundle is not added to the request, and the following message is displayed:
To restrict on-behalf-of entitlements for a specific catalog service
As a catalog administrator, restrict on-behalf-of entitlements for certain services and securely handle sensitive information.
Apex Global uses a catalog service named Investment Proofs that lets end users declare their investments. Hannah, the catalog administrator, has created this catalog service, which is useful for tax calculations in the payroll department.
Because this service is payroll related, Hannah must restrict the entitlements. She logs in to the BMC Digital Workplace Catalog console and restricts the on-behalf-of entitlements for this service. After she's finished, requestors can submit this request only for themselves and not for other employees.
An end user, Britney, is out of the office for a week with low network coverage. The deadline for the final investment declaration is nearing. Britney asks her teammate, Mary, to submit the Investment Proofs request on her behalf.
Mary logs in to the end-user console with the Request as someone else option to submit the request on behalf of Britney. Mary searches for the Investment Proofs service but cannot find it. She informs Britney that she could submit the request only for herself and not on behalf of Britney.
Click here to see the user interface images.
- Mary logs in to the end-user console with her own profile and searches for the Investment Proofs service:
- Mary logs in to the end-user console with the Request as someone else option to submit the request on behalf of Britney, but cannot find it:
Britney has to submit her own Investment proofs request as it is a restricted service.
To restrict the on-behalf-of entitlements for a catalog service
- Log in to theBMC Helix Digital Workplace Catalog console.
- Navigate to Services > Services.
- Select the checkbox for the intended service or double-click a service from the list to enable collaborator delegation.
The user interface displays the Service Options pane. - From Version Options, select the Disable on-behalf-of requests checkbox to restrict on-behalf-of entitlements for that service.
By default, the setting is off.
After this selection, the service version gets updated. With this configuration, only individuals making the request can submit it for themselves; no other user can submit it on behalf of them.