The Processing category refers to settings of the INETAPP that accompany various aspects around handling the ticket processing interfaces and define the behavior.
Basic, general settings.
A supporter can normally select any user from the INETAPP database from the list Who is affected? when opening a ticket. In a multi-tenancy deployment, it is often desired that supporters in First Level of client A do not see the users assigned to clients B and C.
This restriction is set here. The following values are available:
Note: Setting applies to supporters - resource members - without permission as dispatcher and without permission to the application Users and Groups.
Settings for end users in Desktop Application.
Here, the ticket fields that are to be visible to all end users/customers can be determined. This affects the Tickets application as well as the Desktop Application for supporters. The order of the fields can also be freely defined.
Note: The Desktop Application only supports the following columns: Ticket number, Attachments, Subject, Status, Resource, Request date, Category, Priority, Classification, ITIL, Deadline, Identifier, Last agent, Last change date, Free field1-4, as well as 6-7, Total time, Times.
The Bundle tickets... option restricts the conditions under which tickets may be linked to each other. The following options are available:
Note: If bundling multiple tickets is basically possible but restricted by this option, the bundle selection in the menu will be disabled in the ticket list - but remains visible.
Settings that affect resources.
Provides the option of editing tickets - including their attachments - that have already been closed. Often useful when these tickets need to be revised in terms of content. Otherwise, editing the ticket would only be possible by reactivating the task.
Covers the case that the support has met the deadline of a ticket and has finished the ticket, but the customer then only gets in touch after a longer period of time with a note that leads to the reactivation of the ticket and thus to the non-observance of the deadline. Support cannot be held responsible for the customer's delay. The deadline is recalculated from the date of the customer response.
If the support reactivates the ticket, the deadline will be recalculated from that point in time. (for customer phone-support where the supporter reactivates the ticket)
Note: The deadline will only recomputed if the ticket had a deadline before.
Especially if the deadline was set automatically based on the priority when the ticket was created, it may turn out after an initial analysis that the set priority is not applicable and should be changed. However, the new deadline is still directly related to the ticket authorization date.
Note: The deadline will be reset even if the ticket did not have a deadline before.
The 'Link' function us used when independent tickets are to remain in existence, but the orders are related in terms of content. Examples of automatic linking in INETAPP are the ITIL link and the link between a workflow main order and its workflow subtasks.
Certain open tickets are given the 'Resubmission' status, for example when following up on contracts before their expiration date. In the view of 'Open orders', these tickets are often not desired. This checkbox can be used to change the behavior and hide tickets with the status 'Resubmission' from the list of 'Open orders'.
The entering of processing times is interesting if the support provided has to be recorded in terms of time and invoiced. The following options are available for this purpose: