Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Configure a blueprint rule

Configure a rule that contains actions the system can take on blueprint attributes.

Before you begin

Role required: sn_cmp.cloud_service_designer

Procedure

  1. Open a blueprint that has the attribute for which you want to create a rule.

  2. On the Catalog tab, click the operation, such as the provision operation, that contains the attribute.

Image omitted: provision-operation-blueprint.png
Provision operation
  1. In the Variable Sets related list on the Cloud Catalog Item form, click the name of the variable set that contains the variable.

  2. In the Cloud Variables related list on the Variable Set form, click the name of the variable for which you want to crate the rule.

  3. In the Rules related list, click New and then fill in the form.

FieldDescription
NameDescriptionEnter a name and description.
OrderEnter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first.
  1. Right-click the form header and select Save.

Example

This example rule is based on the CloudAccount property and contains an action that tells the system to update the list of locations when the user changes the cloud account.

Image omitted: blueprint-rule.png
An example blueprint rule

What to do next

Configure an optional condition and a mandatory action.

Parent Topic:Build a Cloud Provisioning blueprint

Related topics

Add a resource operation to the execution plan

Execute blueprint operations in parallel

Blueprint attributes

Configure a blueprint rule condition

Configure the condition on a blueprint form event rule that determines when the actions in the rule can run. Conditions are optional.

Before you begin

Role required: sn_cmp.cloud_service_designer

Procedure

  1. Open a rule for a variable on a blueprint.

  2. On the Conditions related list, click New.

  3. Fill out the form fields (see table).

FieldDescription
OperandEnter the property against which you can perform the condiontal evaluation. For example, if your blueprint has a property which holds the value of a datacenter, enter the property name here.
OperatorSelect an operator that evaluates the operand.
ValueEnter a value that the evaluated event rule must match.
Condition Type

If you configure multiple conditions, select the logical operator that determines how the system evaluates the condition in relation to the next condition (the next condition is determined by the Order field):

  • AND: this condition the next condition must meet the criteria before the policy is eligible for execution.
  • OR: this condition or the next condition that matches the criteria can allow the policy to be eligible for execution. If you do not select an option, AND is used by default.
OrderEnter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first.
StatusKeep the status active to have the system process the condition. Change the status to inactive when you do not want the system to process the condition.
  1. Click Submit.

Example

This example condition applies when the user selects the AWS Datacenter for the Logical_Datacenter property, which is a field on the catalog item form:

Image omitted: blueprint-condition.png
Example blueprint condition

What to do next

Configure a blueprint action.

Configure a blueprint action

Configure actions that the system runs when blueprint form attribute actions or event actions are triggered. You can configure actions like making a field mandatory, showing or hiding a field, or automatically populating a field.

Before you begin

Role required: sn_cmp.cloud_service_designer

Procedure

  1. Open a rule for a property or an event on a blueprint.

  2. On the Actions related list, click New and then fill in the form.

FieldDescription
NameUnique and descriptive name.
Action TypeSelect an action type: - Reload: Select a variable to reload - Show: Select a variable to make visible. - Hide: Select a variable to hide. - MakeMandatory: Select a variable to make mandatory. - MakeNonMandatory: Select a variable to make optional. - TriggerChangeEvent: Select a variable on which to trigger a change event. All rules on the selected variable are triggered. - SetValue: Set the value of a variable.
DatasourceSelect an action type: - Reload Cloud Account: - Reload Cloud Location: - Check Quota: - Reload Resource Profile: - Reload From Profile:
Target FieldEnter the name of the field on the form that the action applies to. For example, if you selected TriggerChangeEvent for the action type, the value of the field changes when something changes on the form, as specified in the blueprint rule.
ValueEnter an optional value that you want to assign to the target field. For example, if you selected SetValue for the Action Type field and you want to update the Resource Group Name, you can use the value ${ResourceGroup}, which pulls the names of the resource groups from the blueprint.
OrderEnter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first.
  1. Right-click the header and select Save.

  2. Enter a Key and Value in the KeyValues related list.

    The value in the Value field is applied to the attribute in the Key field.

  3. Create as many actions as necessary.

Example

This example action applies to the blueprint rule example, which is based on the CloudAccount attribute. The action tells the system to update the list of locations when the user changes the cloud account.

Image omitted: blueprint-action.png
Configuring a blueprint action

What to do next

Publish a blueprint as a cloud catalog item.