16 Processes
...
Incident and Request
Configuration
Creating, and then, Closing the Request
4min
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.
It is possible to define the creation and close flow in two different ways:
- It is possible to import the flow with an already registered script.
- Download the attachment JSON Flow and access the flow functionality Tracker > Flow Design
- Click on New,
- Click on Import and select the option JSON.
- Upload the attachment and click on "Import".
- To verify the script, click on the tab Diagram and then on the task icon;
- Finally, click on Input Action;
To copy the script:
- Copy the attachment "Script" content and access the functionality flow Tracker > Flow Design
- Click on "New" and complete the required field.
- 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, click on "Build expressions" and select the register expression.
📌 IMPORTANT!
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.
