---
title: Creating, and then, Closing the Ticket
slug: pink/creating-and-then-closing-the-ticket
description: Learn how to configure the creation and closing of tickets simultaneously for non-SLA activities in this document. Choose between importing a pre-registered script or copying the script content to define the desired flow. Please be aware that information
docTags:
createdAt: 2021-10-27T20:28:05.000Z
---
For activities that do not require an 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
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 a script already registered. Download the attachment "**JSON Flow**" and access the flow
functionality (`Workflow > Flow Design`), click on "**New**", then click on
"**Import**" and select the option "**JSON**". Upload the attachment and click on
"**Import**". Then, to verify the script, click on the tab "**Diagram**" and on the task
icon, next, click on "**Input Action**";
- ******2nd Way - Copy the script****: **to copy only the script, copy the attachment "**Script**" content and access the functionality flow (`Workflow > Flow Design`),
click on "**New**" and complete the field necessary. Then, click on the tab
"**Diagram**", 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 "**Input
Action**". It is necessary to copy the RhinoScript in the expressions builder and
click on "**Build Expressions**" and select the register expression.
:::hint{type="info"}
🖊 **Note****: **No controls have been implemented for catch information because the time
of attendance and closing of the ticket is very short, if it is necessary to
do the same, it will be necessary to implement the registration of the
information in the capture tables.
:::