Accessing Template Management
- Click Templates on the main side bar to view the template list
-
Click Create Template to start a new template
Template Structure
Defining Variables
Variables make templates flexible and reusable. When creating a template, define each variable with:
| Property | Description |
| Variable Name |
Variable identifier (used as `$name` in templates)
|
| Description |
Human-readable label shown in forms
|
Example:
Variable Name: server_name
Description: The name of the windows server
The variable then can be called in any standard change text field by using $server_name
Template Information
| Field | Description | Example |
|
Template Name
|
Unique identifier for the template
|
Server Restart Procedure
|
|
Description
|
What this template is for and when to use it
|
Standard procedure for restarting Windows servers during maintenance windows
|
|
Risk Level
|
Default risk assessmen
|
Low or Medium
|
|
Template Approver
|
The user that has authorised the creation of the standard change template |
Template Content Fields
Each content field supports **variable placeholders** using the `$variable_name` syntax:
Title Template:
A brief, descriptive title that will appear on the change.
Example
"Scheduled restart of $server_name"
Description Template:
Detailed description of what the change involves.
Example
"This change covers the scheduled restart of $server_name as part of
routine maintenance. The restart is required to apply pending updates
and clear system resources.
Server: $server_name
Maintenance Window: $maintenance_window
Estimated Downtime: $downtime_minutes minutes"
Implementation Plan Template
Step-by-step instructions for performing the change
Example:
1. Notify stakeholders of upcoming maintenance
2. Connect to $server_name via RDP
3. Verify no critical processes are running
4. Open Command Prompt as Administrator
5. Run: shutdown /r /t 60 /c "Scheduled maintenance restart"
6. Wait for server to restart (approximately $downtime_minutes minutes)
7. Verify server is accessible and services are running
8. Confirm with stakeholders that services are restored
Test Plan Template
How to verify the change was successful.
Example:
1. Ping $server_name to confirm network connectivity
2. RDP to $server_name and verify login
3. Check Windows Event Log for clean startup
4. Verify all critical services are running:
- Check Service Manager for expected services
- Test application connectivity
5. Confirm uptime shows recent restart
Rollback Plan Template
Steps to revert if something goes wrong.
Example:
If the server fails to restart properly:
1. Access server console via iLO/DRAC/VMware console
2. Check for boot errors or blue screen
3. If stuck, perform hard reset
4. If still failing, boot to Safe Mode
5. Review Event Logs for failure cause
6. Contact $escalation_contact for assistance
7. Document issue in change notes
Auto-Approval
Templates in ChangeBreeze are **automatically approved** when created. This streamlined approach means:
- Templates are immediately available for use
- No separate approval workflow for templates
- The creator is recorded for audit purposes
- Templates can be deactivated if issues are found
Best Practices
Writing Good Templates
1. **Be Specific** - Include exact commands, paths, and procedures
2. **Use Variables Wisely** - Only parameterise what actually changes
3. **Include Verification** - Always have clear success criteria
4. **Document Rollback** - Every template needs a recovery plan
5. **Consider Edge Cases** - What if the change partially fails?
Naming Conventions
Use consistent, descriptive names:
- ✅ "Windows Server Restart - Scheduled Maintenance"
- ✅ "User Account Creation - Standard Employee"
- ❌ "Restart" (too vague)
- ❌ "John's template" (not descriptive)