Change Request Configuration

You can create multiple custom change requests that Commander Admin Portal and Service Portal users may select when they want to request changes to their deployed resources and virtual services. These preconfigured change requests allow you to limit what changes users may request, which users can make those requests, and whether the changes can be made for deployed resources and virtual services or cloud accounts.

You can only create change requests for cloud accounts for Admin Portal users; Service Portal users don't have access to cloud account information and can't request changes for cloud accounts.

Change request visibility

Change requests are less restricted than new service requests:

  • You can define multiple global change requests, and these will be available to all users.
  • You can also create multiple custom change requests and assign them to the same organization, user, or directory service group.

If many change requests are available, when users want to request a change to a deployed resource or virtual service, or to a cloud account, they can choose the most appropriate change request for their needs.

Change request forms

When you create a change request, you can configure whether the change request should display a single-page form to users after they select the change request.

  • Display form — Displaying a change request form allows you to present users with information about the selected resource or virtual service and the changes that will be made to it. The form also allows you to request user input that may be required for the change request.
  • Don't display form — If the change request is straightforward, displaying a form may be unnecessary. Consider a clearly named change request such as "Decommission VM" — this change request would decommission the selected VM, that's it. In such a case, you don't need to include a form to provide extra information or to ask for further user input.

If you want to display a form, when you create the change request you must add form elements to customize the form's appearance and content. The form elements you chose and how you arrange them determine the appearance and content of the form that's presented when users make change requests.

The form elements cover general service settings, as well as component and resource settings used by the resource or virtual service. The component and resource settings that will be available are determined by the components that are included with deployed resources or virtual services. These component-specific and resource-specific settings, can include CPU, memory, network, and estimated cost, for example.

Enable user input

Depending on the form elements you add, when users request a change to a cloud account, deployed resource or virtual service, they may be able to add information to their request or set preferences for it. For example, if you add an Input Text Field to the form, users could note in the change request why they're requesting a memory increase.

You could also add a Custom Attribute element to the form so users could specify a value for that custom attribute. For example, if you add a Project Code custom attribute and make it Required, users would have to provide a project code for the request.

For information on the service-level and component/resource-level form elements that you can add to a change request, see Change Request Form Elements.

Related topics