Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The New Change Template page (/it/changes/templates/new) provides a form for creating reusable IT change request templates. Templates pre-populate the category, implementation plan, rollback plan, test plan, and default risk level when used in the New Change Request form.

​
Overview

The page uses useChangeTemplateMutations for creation. The form collects: name (required), description, category, default_risk_level (low, medium, high), auto_approve (boolean toggle), is_active (boolean toggle, default true), default_implementation_plan, default_rollback_plan, and default_test_plan. On success, navigates to /it/changes/templates. Categories (code-defined): infrastructure, application, security, network, database, other.

​
Who it’s for

No explicit secondary permission gate at the route level beyond the outer ITViewGuard (it.view). Managing templates requires it.changes.manage.

​
Before you start

  • Hold the appropriate changes management permission (it.changes.manage).
  • Define a standard implementation and rollback plan before creating the template.

​
Steps

1

Open the new template form

Navigate to /it/changes/templates/new or click New Template from the Change Templates list.
2

Enter template name and category

Provide a descriptive name (e.g., “Standard Server Patch”) and select the appropriate category.
3

Set default risk level

Choose the default risk level (low, medium, high) that will be pre-selected when this template is used.
4

Configure auto-approval

Toggle Auto-Approve on if standard changes using this template should bypass manual approval.
5

Add default plans

Fill in the default Implementation Plan, Rollback Plan, and Test Plan. These will pre-populate the corresponding fields in new change requests that use this template.
6

Save the template

Click Create Template. On success you are redirected to /it/changes/templates.

​
Key concepts

ConceptDescription
auto_approveWhen enabled, change requests of type standard using this template may bypass the approval queue
is_activeInactive templates do not appear in the template selector on new change request forms
Default plansPre-filled content that users can edit when creating a change request from this template

IT Service Management

IT Service Management overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/it.tsx
  • src/cores/it/pages/changes/NewChangeTemplatePage.tsx
  • src/cores/it/hooks/useChangeTemplateMutations.ts
  • src/cores/it/types/change-management.ts