-
Notifications
You must be signed in to change notification settings - Fork 11
Process configuration
tomolimo edited this page May 21, 2019
·
4 revisions
A click on a process from Plugin process list screen will edit process definition in GLPI.
- Name: is the name of the process.
- GUID: is the global unique identifier for this process.
- Active: Yes/No, select Yes to activate this process in GLPI, and No to de-activate. You may enable or disable a process at any time, but it will only affect start of new cases. Currently running cases will continue their life unaffected.
- Hide...: Yes/No, select No if in the ticket tasks you want to see the 'case number' and the 'case title' in task descriptions. This will affect the future tasks, but not the existing ones.
- Insert...: Yes/No, select Yes if you want to insert task category comments (come from PM server) into GLPI task description. This will affect the future tasks, but not the existing ones.
- Set the maximum cases per GLPI item you authorize for this process. Reset to 0 for unlimited case creation.
- Set to Yes if you want to be able to start cases of this process when in central interface and in incident tickets.
- Set to Yes if you want to be able to start cases of this process when in central interface and in request tickets.
- Ticket type and ITIL category: used when a process is authorized for self-service. In this case, select if the process should be available when creating a ticket for Incident or for Request. And for which ITIL category.
- Set to Yes if you want to be able to start cases of this process in changes.
- Set to Yes if you want to be able to start cases of this process in problems.
- Project type: experimental, don't change this unless you know exactly what you are doing.
- Set to Yes to switch this process in maintenance mode: it will prevent start of new case for this process, and precent any interaction with already started cases.
A click on the 'Synchronize Task List' will refresh the task list.
This list is mainly here to give information, and to verify that translations are correct when editing the task categories.
Note that, you may change the translation from the task category form, but I do not encourage that for the reason that at next 'Synchronize of task list', you'll loose the modifications you've done.
From this form, you may define the authorizations to start a case for the process.
Example: If you want to have a process started by self-service (or post-only) user, you need to:
- define that this process can be started for 'Request' (or 'Incident'),
- define which ITIL category (or ticket category) will be used to start the process. Of course this ITIL category must also be defined as visible in simplified interface and visible for the same type then the process 'Request' (or 'Incident').
- define a right for self-service (or post-only) people to start it in an entity (and recursive yes/no).