---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure a blueprint rule

# Configure a blueprint rule {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

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.  
3. In the Variable Sets related list on the Cloud Catalog Item form, click the name of the variable set that contains the variable.
4. 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.
5. In the Rules related list, click New and then fill in the form.  
   {#configure-a-blueprint-rule__table_osz_gph_xz__entry__2}

   | Field | Description |
   |-|-|
   | Name Description | Enter a name and description. |
   | Order | Enter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first. |
   [ ]

   {#configure-a-blueprint-rule__table_osz_gph_xz}
6. 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.  
Figure 1. Example blueprint rule

## What to do next

Configure an optional [condition](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-blueprint-form-event-conditions "Configure the condition on a blueprint form event rule that determines when the actions in the rule can run. Conditions are optional.") and a mandatory [action](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-blueprint-form-event-actions "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.").
**Related tasks**   

* [Add a resource operation to the execution plan](https://www.servicenow.com/docs/~Xl3biGggpLv1c4EhkqhaA "The base system includes a large set of predefined resource operations. Rarely, you might add a custom operation for a resource.")
* [Execute blueprint operations in parallel](https://www.servicenow.com/docs/q41oDgo9EACnaggStRJiow "You can execute your blueprint resource operations to run in a linear or in a parallel way.")  
**Related reference**   

* [Blueprint attributes](https://www.servicenow.com/docs/cp5Zl~GfLobPefkahmM0gA "When you add a blueprint operation to a resource, the system adds the appropriate attributes. You can choose whether or not to make the attributes available as catalog properties on the form when the system performs the operation.")

## Configure a blueprint rule condition {#ariaid-title2}

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](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-a-blueprint-rule "Configure a rule that contains actions the system can take on blueprint attributes.") on a blueprint.
2. On the Conditions related list, click New.
3. Fill out the form fields (see table).  
   {#configure-blueprint-form-event-conditions__table_k4k_chk_wz__entry__2}

   | Field | Description |
   |-|-|
   | Operand | Enter 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. |
   | Operator | Select an operator that evaluates the operand. |
   | Value | Enter 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. {#configure-blueprint-form-event-conditions__ul_ecr_yhk_wz}If you do not select an option, AND is used by default. |
   | Order | Enter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first. |
   | Status | Keep 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. |
   [ ]

   {#configure-blueprint-form-event-conditions__table_k4k_chk_wz}
4. 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:  
Figure 2. Example blueprint condition

### What to do next

[Configure a blueprint action](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-blueprint-form-event-actions "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.").

## Configure a blueprint action {#ariaid-title3}

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.  
   {#configure-blueprint-form-event-actions__table_nls_lrk_wz__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique and descriptive name. |
   | Action Type | Select 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. {#configure-blueprint-form-event-actions__ul_ep1_g5k_wz} |
   | Datasource | Select an action type: * Reload Cloud Account: * Reload Cloud Location: * Check Quota: * Reload Resource Profile: * Reload From Profile: {#configure-blueprint-form-event-actions__ul_kpm_v5k_wz} |
   | Target Field | Enter 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](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-a-blueprint-rule "Configure a rule that contains actions the system can take on blueprint attributes."). |
   | Value | Enter 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. |
   | Order | Enter a number that tells the system which record to evaluate first in relation to others. The record with the lowest number runs first. |
   [ ]

   {#configure-blueprint-form-event-actions__table_nls_lrk_wz}
3. Right-click the header and select Save.
4. **Optional:** 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.
5. Create as many actions as necessary.

### Example

This example action applies to the [blueprint rule
example](https://www.servicenow.com/docs/mkV44JlrjQeHD3mu5wOJqQ#configure-a-blueprint-rule "Configure a rule that contains actions the system can take on blueprint attributes."), 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.Figure 3. Example blueprint action

### What to do next

[Publish a blueprint as a cloud catalog item](https://www.servicenow.com/docs/es9WG5b_CqIBFwnjxKcX~Q "You can create and publish a catalog item directly from a blueprint.").