Order form customization on CloudBolt Documentation

Networking

Mon, 01 Jan 0001 00:00:00 +0000

The available networks depend on the group and environment selected on the order form.

Choose which networks are available

Control which networks a group can use on its Networks tab. You need permission to manage the group’s networks.

Go to Groups and select a group to open its details.
Select the Networks tab. Each row is a network associated with the group, and each column is a NIC. Use the NIC columns to show selector to set how many NIC columns appear (1 to 10; four by default).
In the cell where a network and a NIC intersect, use the toggle to make that network available on that NIC.

Environments work the same way: go to Admin > Environments, select an environment, and open its Networks tab. In some environments, such as AWS and Azure, the tab also has an import button (Import Subnets, or Import VPC Subnets in an AWS environment) that brings in subnets before you enable them.

Order on behalf of a recipient user

Mon, 01 Jan 0001 00:00:00 +0000

By default, the person who submits an order (the requestor) owns the servers and resources it creates. When the Recipient field is enabled on the order form, a permitted user can instead assign ownership to another user.

Enable the Recipient field

An admin controls when the Recipient field appears with the Miscellaneous Setting Show “Recipient” on Order forms (Admin > Miscellaneous Settings, Resource Management tab). It has three options:

When Allowed: the field appears for all permitted users.
Only Enabled Blueprints: the field appears only on blueprints that a blueprint manager has enabled it for. To enable it on a blueprint, select Edit on the blueprint’s Overview tab and turn on Show “Recipient” field on order form.
Never: the field is hidden, and the requestor is the sole recipient. This is the default.

Who can set and receive

Even when the setting allows it, the Recipient field appears only for users with the order.choose_recipient permission in the selected group. By default, no standard role includes this permission; only super admins have it. To let other users choose a recipient, add order.choose_recipient to a role and assign that role in the relevant group.

T-shirt sizing for VMs

Mon, 01 Jan 0001 00:00:00 +0000

Use preconfigurations to bundle a group of options into a single choice on the order form. This lets you offer a friendly, technology-agnostic set of sizes (such as small, medium, and large) that align with your corporate standards for server ordering.

Different resource handlers use different size parameter names: AWS uses instance_type, Azure uses node_size, GCP uses gcp_node_size, and vCenter uses cpu_cnt, mem_size, and disk_size. The vCenter parameters are built in. The AWS, Azure, and GCP parameters are created when the matching resource handler is configured, so they appear in a preconfiguration’s Custom fields list only after that handler exists.