---
title: How to create, and then, close the ticket
slug: citsmart-8-en/how-to-create-and-then-close-the-ticket
description: Learn how to automate ticket creation and closure for non-SLA activities in your ticketing system. This document provides step-by-step instructions for configuring the system using pre-registered or manual script setup. Please note that additional measure
docTags: 
createdAt: 2022-01-19T22:58:59.000Z
---

For activities that do not require an SLA, where the attendant only wishes to&#x20;formalize the request and execution of the activity, it is possible to configure&#x20;for the creation and closing of the ticket at the same time.

## Procedure

1 - It is possible to define the creation and close flow in two different ways:

- **1st Way - Import flow**: it is possible to import the flow with the script already  &#x20;registered. Download the attachment "**JSON Flow**" and access the flow  &#x20;functionality (`Workflow > Flow Design`), click on "**New**" then on  &#x20;"**Import**" and select the option "**JSON**". Upload the attachment and click on  &#x20;"**Import**". To then verify the script, click on the tab "**Diagram**" and the task  &#x20;icon. Next, click on "**Input Action**";
- **2nd Way - Copy the script**: to copy only the script, copy the attachment  &#x20;"**Script**" content and access the functionality flow (`Workflow > Flow Design`),  &#x20;click on "**New**" and complete the mandatory fields. Then click on the tab  &#x20;"**Diagram**" to design the creation and closure flow of a task. Select and  &#x20;click on this task (small gray box next to the task), and in the tab "**Input  &#x20;Action**". It is necessary to copy the RhinoScript in the expressions builder and  &#x20;click on "**Build expressions**" and select the register expression.

:::hint{type="info"}
🖊 <u>**Note:**</u>

No controls have been implemented to catch information because the time
of attendance and closing of the ticket is very short.

If it is necessary to&#x20;do the same, implement the information registration in the capture tables.
:::

