# Field Configuration

This module is part of the Automation framework in Infraon ITSM. It provides administrators and privileged users with the ability to define how fields behave across various ITSM modules, including **Tickets, Requests, Problems, Changes, and Releases**.

Field configurations determine whether a field is visible, mandatory, or disabled for a specific role at a particular stage in the workflow. Safeguarding every role, from requesters and technicians to managers and approvers, only interacts with the fields relevant to their responsibilities.

Additionally, any changes made here are also reflected in the **Self-Service Portal (SSP)**, ensuring consistency between the admin console and the end-user interface.

## **What do you see on the screen**

The page provides an overview of all configurations created within the platform. From this screen, administrators can:

* **Add new configurations** using the **+ Add Field Configuration** button.
* **View, edit, or delete** existing configurations through the action icons.
* Switch between **card view** and **grid view** for better visualization.

## **Add Field Configuration**

To create a new field configuration, navigate to the **top-right corner** of the page and click on the **+ Add Field Configuration** button.

**Add Field Configuration |** Basic Details

<table><thead><tr><th width="169">Label</th><th width="208.2000732421875">Action</th><th>Description / Example</th></tr></thead><tbody><tr><td><strong>Module</strong></td><td>Select from the drop-down.</td><td><p>Defines the ITSM module to which the configuration applies. <br><br><strong>Options include:</strong><br></p><ul><li>Ticket</li><li>Service Request</li><li>Problem</li><li>Change</li><li>Release</li><li>Contract Management</li></ul></td></tr><tr><td><strong>Workflow</strong></td><td>Select from the drop-down.</td><td><p>Refers to the workflow process associated with the selected module. Each module can have one or more workflows (e.g., Ticket Workflow, Request Workflow, Change Approval Workflow).</p><p></p><p><strong>Example:</strong> If Request__Workflow is selected, the configuration will be tied to that specific request lifecycle.</p></td></tr><tr><td><strong>Type</strong></td><td>Select from the drop-down.</td><td><p>Defines the type of configuration being created:<br><br><strong>Field Configuration:</strong> Allows admins to control how fields behave within the workflow.<br><br><strong>Example:</strong><br></p><ul><li>View: Field is visible but not editable.</li><li>Disable: The Field is greyed out and cannot be interacted with.</li><li>Mandatory: Field must be filled before moving to the next status.</li></ul><p><strong>Notification Configuration:</strong> Controls when and how system notifications are triggered for the selected module and role.<strong>Example:</strong> Sending an approval email when a ticket moves to the Approval status.</p></td></tr><tr><td><strong>Role Name</strong></td><td>Select from the drop-down.</td><td>Specifies the roles for which this configuration will apply. Roles represent user groups such as IT Manager, Requester, NOC Operator, Admin, Technician, etc.</td></tr><tr><td><strong>Status</strong></td><td>Select from the drop-down.</td><td>Indicates the workflow stage(s) where the configuration will be enforced. Statuses vary depending on the module and workflow (e.g., New, In Progress, Pending for User Input, Approval, Resolved, Closed).<br><br><strong>Example:</strong> Setting the field as Mandatory in the Approval stage ensures the field must be filled before the record moves forward.</td></tr><tr><td><strong>Notify To</strong></td><td>Select from the drop-down.</td><td><p>Available only if <strong>Type = Notification Configuration</strong>. Defines who will receive notifications when the configured rule is triggered.<strong>Options include:</strong><br></p><ul><li><strong>Group Email ID:</strong> Send notifications to a shared group mailbox.</li><li><strong>Team Member:</strong> Notify a specific team member.</li><li><strong>Team Level Members:</strong> Notify all members of the assigned team.</li><li><strong>Requester:</strong> Notify the requester who raised the ticket or request.</li></ul><p><br><strong>Example:</strong> Notify the Requester when a Service Request moves to Resolved</p></td></tr></tbody></table>

![](/files/8a8ee72778e8d436d9af19922ef046932d7fadde)

Once the **basic details** (Module, Workflow, Type, Role Name, and Status) are selected, admins can define how each field should behave for the chosen workflow stage and role.

You can configure system-provided **General Fields** (such as Status, Impact Service, Team, Assignee, Subject, Urgency, Impact, Priority) as well as **custom fields** created in the workflow. Additionally, fields like Reported By can also be included in the configuration.

For each field, admins can set one of the following actions:

* **View:** Field is visible but cannot be modified.
* **Disable:** Field is completely disabled for the role at the selected status.
* **Mandatory:** Field must be filled in before progressing to the next workflow stage.

Admins can click the respective action icons to confirm the field’s configuration.

{% hint style="info" %}
The list of available fields will vary depending on the **module** (Ticket, Request, Change, etc.) and the **workflow** selected.
{% endhint %}

Once all field rules have been defined, click **Submit** to save the configuration.

![](/files/941d5e9376943b745afb644460b24f0f6c86134c)


---

# Agent Instructions: 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:

```
GET https://docs.infraon.io/infraon-help/infinity-user-guide/infraon-configuration/infraon-automation/field-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.