Cloud catalog form configuration examples
Several examples are provided to help you understand how to manipulate Cloud catalog order forms. These example cover blueprint rules, blueprint variables, and blueprint form UI groups.
| Example | Goal | Blueprint components used |
|---|---|---|
| Populate the location based on the cloud account | Use existing blueprint rules to illustrate how the Location field is populated based on the Cloud Account that the user selects. | This example illustrates rules. |
| Remove a field from a cloud catalog form | Hide the Cost Center field on the catalog form when the catalog requester belongs to the Database group. | This example illustrates:
|
| Populate stack name with a script | Give the catalog requester a pre-defined stack name that includes the ID of the catalog requester. The field remains editable to the user can change it if necessary. | This example illustrates:
|
| Add fields to a cloud catalog item order form | Create a catalog variable and property, and use it to publish a new filed on a form. | This example illustrates:
|
| Set default values for a cloud catalog form fields | Set a default value on a property and on a blueprint rule. | This example illustrates:
|
| Add a UI group with additional fields | Group catalog form fields into tabs to better organize the form and guide the user from one set of settings to another. | This example illustrates UI groups (tabs). |