Перейти к содержимому

Unboxing Scaled (Major Changes) with Demo

Learn N Grow Together With Atul G

0:00 / 0:00

Unboxing Scaled (Major Changes) with Demo

132 просмотра · 2 дня назад
Learn N Grow Together With Atul G
17,1 тыс. подписчиков
132 просмотра · 2 дня назад
Brazil Feature ‪@ServiceNowDocs‬ ‪@servicenow‬ ‪@ServiceNowDevProgram‬ Scaled Change extends change management to complex environments with many configuration items. A single Scaled Change generates and coordinates child change records for every affected configuration item. It uses scheduling intelligence, conflict detection, and approval workflows to keep large-scale changes on track from planning through closure. Use scaled change when a single change affects many CIs and you need to track implementation for each CI separately. Add all affected CIs to one Primary change request. When the Primary change reaches its configured trigger state, one Child change is generated for each CI. For example, a Primary change with 20 affected CIs generates 20 Child changes. Generate child changes using Scaled change Scaled change generates Child changes in the following sequence: A Primary change is created using a change model configured to allow Child change creation on a configured trigger state. For example, if the configured trigger state is Assess, Child changes are generated when the Primary change enters Assess. When the Primary change enters the configured trigger state, one Child change is generated for each CI in the Affected CIs list. Each Child change's configuration item is set to the corresponding CI. Its short description, category, description, justification, implementation plan, risk and impact analysis, backout plan, and test plan are copied from the Primary change. While generation is in progress, the Primary change's child_changes_creation_status field is set to in_progress. When all child changes are generated, child_changes_creation_status is set to completed, or completed_with_errors if any child change failed to generate. Scaled change implementation To implement scaled change, complete the following tasks in order: Create a Primary change model and configure a trigger state with the Allow Child Change Creation attribute. For more information, see Configure a Primary change model. Create a Child change model. For more information, see Configure a Child change model. Create a flow to configure child change creation on the Primary change model. The flow triggers when the Primary change reaches the configured state. For more information, see Create a scaled change flow. Note: To configure the system properties related to child change creation, see Components installed with Scaled Change.