---
title: Creating, and then, Closing the Request 
slug: helium-en/creating-and-then-closing-the-request
description: Learn how to easily configure the creation and closing of non-SLA tickets with step-by-step instructions in this comprehensive document. Whether you choose to import a pre-registered script or copy and paste the script content, we'll guide you through the
createdAt: 2021-10-18T19:24:45.000Z
---

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

## Procedure

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

### Import flow&#x20;

1. It is possible to import the flow with an already registered script.&#x20;
2. Download the attachment **JSON Flow** and access the flow functionality `Tracker > Flow Design`&#x20;
3. Click on **New**,&#x20;
4. Click on **Import** and select the option **JSON**.&#x20;
5. Upload the attachment and click on "**Import**".&#x20;
6. To verify the script, click on the tab <font color="#2166ae">**Diagram**</font> and then on the task icon;&#x20;
7. Finally, click on **Input Action**;

### Copy the script:

To copy the script:

1. Copy the attachment "**Script**" content and access the functionality flow `Tracker > Flow Design`&#x20;
2. Click on "**New**" and complete the required field.&#x20;
3. Click on the tab "<font color="#2166ae">**Diagram**</font>", design the flow about the creation and closure of a task, select and click on this task (small gray box next to the task) and in the tab "<font color="#2166ae">**Input Action**</font>".&#x20;
4. It is necessary to copy the RhinoScript in the expressions builder, click on "**Build expressions**" and select the register expression.

:::hint{type="warning"}
📌 <u>**IMPORTANT**</u>**!**

No controls have been implemented to gather information because the time of attendance and closing of the ticket is very short. Should it be necessary to do the same, it'll be necessary to implement the registration of the information in the capture tables.
:::

