From the Plugin Process List, you may edit a process definition (or configuration):
- You may synchronize task list. Tasks are imported from Process Maker Server, with some information like Name, Complete Name (is completed with root Task Category and Process Name), ProcessMaker Task UID, a flag to indicate which task will be started when a case is started for this process, and Comments.
- You may configure the process like following:
a) Is the process active? 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.
b) Will case number (case #) and case title hidden in GLPI Ticket Tasks Descriptions. This will affect all new created tasks, but not the existing ones.
c) Will Task Category (=Task Name) inserted into comments of GLPI Ticket Tasks? This will affect all new created tasks, but not the existing ones.
d) What will be the type and category (class) of Tickets created via simplified interface (this setting is used only when creating ticket via ProcessMaker plugin in simplified interface). This will affect all new created ticket/case, but not the existing ones.
This defines the rights to start a new case. You have to set Entity/Profile to define the profiles that will have the rights to start a case on which entities.
This is working the same way than for defining authorizations for users in GLPI.
In this example:
- 'post-only' profile will be able to start a 'Credit Card Application' case wherever they want, as it is authorized from 'root' entity and recursive.
But as 'post-only' profile is defined for 'simplified interface', then 'post-only' users will be able to start a case only when using the plugin 'helpdesk' interface see Pluging Simplified Interface.
- 'super-admin' profile will be able to start a case for this process only when in the 'root' entity as it is not defined as recursive.
You may add any authorization lines you need: there is no restriction.