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 Request page (/it/changes/new) provides a three-tab form for creating an IT change request: Basic Info, Risk Assessment, and Planning. The request can be saved as a draft or submitted immediately for approval.

​
Overview

The page uses useChangeRequestMutations for creation and useChangeTemplates to populate the optional template selector. Selecting a template pre-fills category, implementation_plan, rollback_plan, and test_plan. Risk assessment uses RiskAssessmentForm collecting impact_score, likelihood_score, and rollback_complexity_score (each 1–N scale; SME: confirm scale range). Change types (code-defined): standard, normal, emergency.
Categories (code-defined): infrastructure, application, security, network, database, other. Saving as draft sets status: 'draft'. Submitting for approval sets status: 'submitted'.

​
Who it’s for

No explicit secondary permission gate beyond the outer ITViewGuard (it.view). Creating changes requires it.changes.create.

​
Before you start

  • Have a clear description of the change, its purpose, and a rollback plan before starting.
  • Check if an existing change template applies to your scenario.

​
Steps

1

Open the new change request form

Navigate to /it/changes/new or click New Request from My Change Requests or the Changes list.
2

Select a template (optional)

In the Basic Info tab, optionally select a template from the dropdown. This pre-fills the Category, Implementation Plan, Rollback Plan, and Test Plan fields.
3

Fill in basic information

Enter a title (required), description, change type (standard, normal, or emergency), and category.
4

Complete the risk assessment

Click the Risk Assessment tab. Fill in impact score, likelihood score, and rollback complexity score using the RiskAssessmentForm.
5

Fill in planning details

Click the Planning tab. Fill in the implementation plan, rollback plan, and test plan.
6

Save or submit

Click Save Draft to save without submitting, or Submit for Approval to enter the approval workflow.

​
Key concepts

ConceptDescription
change_typestandard (pre-approved), normal (requires approval), emergency (expedited)
status: 'draft'Saved but not submitted; only the creator can see and edit
status: 'submitted'Submitted for approval review
RiskAssessmentFormCollects three numeric scores that contribute to computed risk level

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/NewChangeRequestPage.tsx
  • src/cores/it/hooks/useChangeRequestMutations.ts
  • src/cores/it/hooks/useChangeTemplates.ts