---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create a scaled change flow

# Create a scaled change flow {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Create a flow to configure child change creation on the primary change model. The flow triggers when the primary change reaches the configured state.

## Before you begin

Role required: `sn_change_write or itil`

* Activate the Major Change (com.sn_major_change) plugin. For more information, see [Activate a plugin](https://www.servicenow.com/docs/access?context=t_ActivateAPlugin&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). This plugin includes the Child change requests creation action that the flow uses.
* Create a Primary change model. For more information, see [Configure a Primary change model](https://www.servicenow.com/docs/KMuC4nEBJRCuKx6ReXVEbQ "Configure a Primary change model so that a change using this model generates one Child change for each affected configuration item (CI).").
* Create a Child change model. For more information, see [Configure a Child change model](https://www.servicenow.com/docs/xm96rjzOriHaiiTP94gKAw "Configure a Child change model to define the states required by the Child change requests.").

## Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Select New, and then select Flow.  
   For more information about Flow Designer, see [Create a flow in Workflow Studio](https://www.servicenow.com/docs/access?context=create-flow&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US).
3. Enter a name in the Flow name field, and select Build flow.
4. Configure the flow trigger.  
   {#create-a-scaled-change-flow__table_flow_trigger__entry__2}

   | Setting | Value |
   |-|-|
   | Trigger type | Record Created or Updated |
   | Table | Change Request \[change_request\] |
   | Condition | \[Model\] \[is\] \[Scaled change\] and \[State\] \[is\] \[Assess\] |
   | Run Trigger | Only if not currently running |
   [Table 1. Flow trigger configuration]

   {#create-a-scaled-change-flow__table_flow_trigger}

   Use the name of your own Primary change model in the Model condition.
5. Add the Child change requests creation action, and set its change model input to your Child change model.  
   This action creates one Change Management Worker record for each batch of CIs that does not already have a Child change. It also sets the Primary change's `child_changes_creation_status` field to
   `in_progress`.
6. Add a condition that ends the flow if the Child change requests creation action reports that the request was not processed.
7. Add a Wait For Condition action on the Change Request table where Child changes creation status is Completed, or Completed with Errors.
8. Add the Evaluate Change Model action.  
   This base-system action evaluates the next available state for the change based on its change model. It moves the Primary change to the next state after Child change generation completes.
9. Select Publish.

## Result

When a change using the Primary change model enters the configured state, the flow creates one Child change for each configuration item (CI) in the Affected CIs list. Each Child change copies category, description,
justification, implementation plan, risk and impact analysis, backout plan, test plan, and software model from the Primary change.

To view child changes on a primary change request, select Configure, select Related Lists, and add the related list driven by the `primary_change` field. This related
list displays the child changes generated for a primary change. It is hidden until child changes are created and does not appear on a child change.

Child changes generated from a Primary change have the Configuration item and Model fields set to read-only.

*[\>]: and then