|
Australia
|
- **[Granular admin role](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=australia&ft:locale=en-US)**
Assign the single feature-specific granular sn\_change\_admin role to users to grant permission to configure Change Management features and system properties. This role replaces the previous general admin and ITIL roles. The sn\_change\_admin role includes the sn\_change\_writer, change\_manager, and sn\_change\_cab.cab\_manager roles.
- **[Exclude change request records from conflict check](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=australia&ft:locale=en-US)**
Exclude change requests from the conflict check process by setting the **Exclude from conflict detection** field to true. This setting also means that the change record is not displayed as a conflicting change when conflict checker is run on other change records.
- **[Create change templates](https://www.servicenow.com/docs/access?context=create-change-template&family=australia&ft:locale=en-US)**
Control mandatory and read-only fields for change models by configuring change templates and defining template field policies. Change templates provide baseline standardization for common changes, making changes easier to create as well as driving a higher standard of change and compliance. Similar to the concepts used for existing standard change templates, templates used for change models can be proposed, reviewed, versioned, or retired.
- **[Enhanced data model for change templates](https://www.servicenow.com/docs/access?context=change-data-model&family=australia&ft:locale=en-US)**
Use the enhanced data model that supports better categorization and role-based access for change templates for all change models automatically. This feature is optional for newly created standard changes.
This data model does not impact the existing standard change catalog and migration of these standard changes is not required.
|
|
Brazil
|
- **[Compliance dynamic schema](https://www.servicenow.com/docs/access?context=compliance-dynamic-schema&family=brazil&ft:locale=en-US)**
Store risk and compliance details on change requests without adding columns to the Change Request table. Compliance dynamic schema saves these details as name and value pairs in a single field using the platform Dynamic Schema feature. Regulated industries can capture information such as whether a change handles personal data, whether an audit trail is required, and how long a rollback takes. The base system includes example dynamic categories such as Risk and Compliance, Financial Risk and Compliance, and SaaS/Cloud Security Compliance, and example attributes covering areas such as audit trail, downtime, estimated impacted users, lead time, rollback time, and compliance. You can deactivate the examples and define categories and attributes that match your organization's compliance requirements. You can also read and update attribute values from scripts, including risk condition scripts and business rules, using the dynamic schema scripting API.
- **[Change lockdown](https://www.servicenow.com/docs/access?context=change-lockdown&family=brazil&ft:locale=en-US)**
Change lockdown allows change managers to pause all or a subset of in-flight change requests. Use it during major unplanned IT, critical, or financial events.
**Note:** The Change lockdown depends on Change Management - Collision Detector plugin \(com.snc.change.collision\), this plugin is now activated automatically when you upgrade to the Brazil release.
- **[Change lockdown conflict detection](https://www.servicenow.com/docs/access?context=lockdown-conflict-detection&family=brazil&ft:locale=en-US)**
Automatically flag change requests that overlap an active lockdown period. Conflict detection runs alongside maintenance window and blackout window checks. Any change request inside a lockdown is marked as an Inside Change Lockdown conflict and placed on hold. Reschedule it outside the lockdown period to clear the conflict and continue processing.
- **[Scaled change](https://www.servicenow.com/docs/access?context=scaled-change-overview&family=brazil&ft:locale=en-US)**
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.
- **[ITIL change process assignment for change models](https://www.servicenow.com/docs/access?context=itil_change_process_models&family=brazil&ft:locale=en-US)**
Assign an ITIL change process to a change model so the ChangeRequest API uses that model when it creates a matching change request.
- **[State field policies for change models](https://www.servicenow.com/docs/access?context=state-field-policies-change-models&family=brazil&ft:locale=en-US)**
Use state field policies to make change request fields mandatory or read-only at each state in a change model. Policies are enforced on the form when a change request is created or updated.
|