> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/configuring-application-settings/change-request-application-settings/change-type.md).

# Change Type

Define change types and assign default reviewers.

## Overview

The **Change Type** module provides tools to manage classifications for change requests. It allows you to:

* **Define & Manage Change Types**
  * Create and maintain categories for different types of changes based on their impact or scope.
* **Assign Default Reviewers**
  * Designate a default reviewer for each change type to ensure proper oversight and approval.

***

## How Settings Are Applied

Change types defined in this module appear in the **Change Type** dropdown of the [**New Change Request**](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/create-new-change-request.md) form.

{% hint style="warning" %}
When a change type is selected, the designated reviewer automatically populates the **Reviewer** dropdown.&#x20;

* Users can manually override this assignment if necessary.
  {% endhint %}

***

## Defining & Managing Change Types

Follow these steps to create, edit, and maintain change types:

{% stepper %}
{% step %}

### Defining Change Types

Click **Add** to create a new change type.

<details>

<summary><mark style="color:blue;"><strong>Add Change Type</strong></mark></summary>

The **Add Change Type** form allows you to define new change types and assign appropriate reviewers.

{% hint style="warning" %}
When creating a new change type, you must either select a predefined category from the dropdown or define a custom category.

* If a predefined category is chosen, the **User-Defined Change Category** field will be hidden.
  {% endhint %}

1. **Define Details**

Complete the relevant fields to configure the change type.

* **Change Category:** Select a [predefined category](#user-content-fn-1)[^1].
* **User-Defined Change Category:** If no predefined category fits, enter a custom category.
* **Reviewer:** Select the party responsible for reviewing the category.

{% hint style="info" %}
The **CR Manager** dropdown dynamically loads active users, roles, and groups in the system. These entities are managed in **Library** > **Organization**.
{% endhint %}

***

2. **Save Changes**

When ready to save, choose one of the following options:

* **Save and Return:** Click to save the change type and return to the main form.
* **Save and New:** Click to save the change type and open a new form to create another.

</details>

***

{% endstep %}

{% step %}

### Managing Change Types

Once a change type is defined, the following actions are available:

* [**Edit**](#user-content-fn-2)[^2] ( <i class="fa-pencil">:pencil:</i> ): Click to modify a change type.
* **View** ( <i class="fa-eye">:eye:</i> ): Click to open a change type in read-only mode.
* **Delete** ( <i class="fa-trash-can">:trash-can:</i> ): Click to remove a change type.

{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undo** ( <i class="fa-arrow-rotate-left">:arrow-rotate-left:</i> ).
{% endhint %}

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How to Export Grid Data</strong></td><td>Export grid contents to an Excel file.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F8EURtbR8olEYsY7knlFB%2FIMS-V16-NAV-Library-Icons-106.png?alt=media&amp;token=7664c54c-4826-48e4-8ca0-d042582c2f2d">IMS-V16-NAV-Library-Icons-106.png</a></td><td><a href="https://interfacing.gitbook.io/interfacing-help-files/end-users/exploring-apps/working-with-forms/working-with-grids#exporting-data-to-excel">https://interfacing.gitbook.io/interfacing-help-files/end-users/exploring-apps/working-with-forms/working-with-grids#exporting-data-to-excel</a></td></tr></tbody></table>

[^1]: The following are the available predefined categories for selection:

    * **Document Change**: For modifications to controlled documents, procedures, or work instructions.

    - **Process Change**: For modifications to business processes, workflows, or operational methods.

[^2]: You can also **double-click** the row to edit quickly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/configuring-application-settings/change-request-application-settings/change-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
