# Create Workflow

Upon creating a ticket/change/problem/request, the default status is 'Open,' situated at the top of the status hierarchy. Additional statuses can be arranged below 'Open' through drag-and-drop functionality. The final status will typically be either 'Closed' or 'Resolved.'

**Build Form | Configure Windows** 

Configure Windows has three sections: State, Actions, and If Conditions. To complete the workflow, these drag-and-drop HTML elements are placed in the 'Configure Windows' area.

**State | Actions | If Conditions**

<table data-header-hidden><thead><tr><th width="166"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong> </td><td><strong>Action</strong></td><td><strong>Description</strong> </td></tr><tr><td>Open </td><td>By default, the state is open and new.</td><td>This is the initiation of workflow.</td></tr><tr><td>In Progress </td><td>Drag the in-progress button below the open state.</td><td>showsThe In-progress state is added to show that the workflow is in a progressive state. You may add the In-Progress button and define the state and status.</td></tr><tr><td>Approval</td><td>Drag the Approval button below the 'in-progress' state, 'on-hold' or 'open' state.</td><td>Approval shows that the workflow status is in an approval state for acceptance or rejection by the approval team. You may configure the Approval button and define the state and status.</td></tr><tr><td>On Hold </td><td>Drag the on-hold button below the open or the In-progress state.</td><td>On Hold shows that workflow is on hold due to some conditions. You may configure the On Hold button and define the state and status.</td></tr><tr><td>Resolved </td><td>Drag the resolved button directly after the 'open' or below the 'in-progress' or 'on-hold' state.</td><td>Resolved shows that workflow status is being resolved. You may configure the Resolved button and define the state and status.</td></tr><tr><td>Close </td><td>Drag the Close button after the Resolved state.</td><td>Close shows that the workflow status is being closed. You may configure the Close button and define the state and status.</td></tr></tbody></table>

{% hint style="info" %}
PIR ( Post Implementation Review) - This functionality is a post-implementation review for valuable insights and feedback about the change implementation. Infraon determines the review team that comments on the process and delivers feedback on the implementation process, including problems faced and resolutions given. This enhances ITSM workflows, facilitating continuous improvement.
{% endhint %}

**State | Actions | If Conditions**

Actions are performed after the state is defined.

<table data-header-hidden><thead><tr><th width="203"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong> </td><td><strong>Action</strong> </td><td><strong>Description</strong> </td></tr><tr><td>Transfer State </td><td>Drag Transfer state if you want to change a specific state and status.</td><td>It generally comes after the 'If Conditions' button is applied to change or set the original state.</td></tr><tr><td>Set Value </td><td>Drag the Set value button under any state to set the predefined value.</td><td>Set Value has five operands: Priority, Status, Impact, Urgency, and Severity. And, It has three values: High, Medium, and Low. Set any operand to the desired value.</td></tr><tr><td>Send Email </td><td>Drag Send Email button under any state.</td><td>To, Subject, and Description boxes must be added to proceed further. Select one value from the dropdown menu to add the 'To' box, and write on the subject and description box. Click 'Save' to save it.</td></tr><tr><td>Send SMS </td><td>Drag Send SMS under any state.</td><td>Add 'To' and Description boxes to proceed further. Select one value from the dropdown menu to add the 'To' box, and write on the description box. Click 'Save' to save it.</td></tr></tbody></table>

Enhanced change management by introducing the "Ask for Change" functionality. This replaces the rejection option and allows changes to be requested during the review process. The transition state is activated upon request for changes, facilitating a seamless transition to the open state for effective change management.

**State | Actions | If Conditions**&#x20;

<table data-header-hidden><thead><tr><th width="190"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong> </td><td><strong>Action</strong> </td><td><strong>Description</strong> </td></tr><tr><td>If Conditions </td><td>Drag the 'If Conditions' button under any state to implement conditions.</td><td>You can later configure conditions by putting correct values. 'If Conditions' has four sections: Operand, Operator, value, and Relation. Based on Operand and Operator selection, Value selection shows varying options. You can add more 'Relation' 'ADD' or 'OR' from the dropdown menu.</td></tr></tbody></table>

{% hint style="info" %}
**Note:** Since conditions are optional, you can publish the incident workflow without adding them.
{% endhint %}

## Email Notification for approval process:

Enhanced approval functionality in workflows, such as the ticket workflow. Easily add an approval state with options for approval and rejection. Configure email settings when the approval is accepted, triggering automatic email notifications. This functionality applies to all workflows, ensuring efficient communication and streamlined approval processes.


---

# 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/workflow/create-workflow.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.