Skip to content

Concept

Jump to bottom
tomolimo edited this page Nov 4, 2019 · 14 revisions

You'll find a good documentation about ProcessMaker Server: https://wiki.processmaker.com/3.1/index And to be read before using PM plugin: https://wiki.processmaker.com/3.1/user_guide

Basics between PM and GLPI

Note: GLPI item is used in this wiki to speak about Ticket, Change or Problem.

  1. Process: is the definition of a business workflow (=BPMN, see: Business Process Model and Notation.
  2. Case: is an instance of a Process. This instance is mapped to a GLPI item (=Ticket, Change or Problem). That's the role of the PM plugin.
  3. Tasks: these are the process tasks. these are mapped to GLPI item tasks (one to one). Consequently, the notifications are the one of the GLPI item tasks, and as these tasks are scheduled, they will appear on the people planning. One task can be assigned to a person or to a group. When assigned to a group, the task is 'to be claimed'(= someone should claim for it to be assigned to it before executing it). See tasks
  4. Dynaforms: these are the forms used in PM server. See dynaforms
  5. Case variables: these are the variables used in a case. These variables can be read/write by the PM plugin. See case variables
  6. GLPI is the pilot (or the driver, or the master) of the processes. In current plugin version, the ProcessMaker server scheduled tasks can't be used in the processes.
  7. PM server is then a slave: the 'cases' can't evolve by themselves. Only users assigned to a PM task can run a case and make it evolve in a GLPI item.
  8. The plugin can manage sub-processes. See: Sub-processes.
  9. GLPI groups and users are mapped into PM groups and users.
  10. To insure security and confidentiality, passwords of users mapped into PM are not known and are randomly generated by the plugin and are regularly reset. This to prevent that one person will approve something that should be approved by someone else.
  11. When a case is started (=created) in a GLPI item, some information from the GLPI item are sent to the case, and will be available as case variables. See: Case-Variables.
  12. When a case is derived (goes from one task to another), some case variables are read by the plugin and are used to perform some actions on the GLPI item tasks (the task that just finished and the task that just started).
  13. Notifications are managed by the task notifications in GLPI. But it is possible to use dedicated notifications that are linked to a task and an event (task add, task re-assign, and task close). Also it is possible to send spontaneous emails. To get more information about notifications and emails, see: Notifications
  14. See the Process Design wiki which is very good here: https://wiki.processmaker.com/3.2/Processes

Workflow execution

Case => is an running instance of a process. A case is embedded into a GLPI item and viewed in a dedicated tab (called 'Process - Case').

  • As many cases as you want may be started in a GLPI item. You may limit this, see Plugin-configuration and Process-configuration.
  • A new case (for an active process) can be started at any time for a GLPI item.
  • At creation, status of the newly created case is 'DRAFT': when in this status, a case can be deleted by anybody.
  • Running status of a case is 'TO_DO': in this status, a case can only be 'CANCELLED' (or 'COMPLETED' when finished)
  • Completed (= finished) case status is 'COMPLETED'
  • A case can be deleted if the current profile has been authorized to delete cases.

Task => Tasks from a running cases are mapped to GLPI item tasks. They are dynamically added to the GLPI item during the running of the case.

  • When a new PM task is activated (or routed to), then a new task is created in the GLPI item. Assigned technician to the task is set accordingly to the assignee in PM process definition (or group).
  • When a PM task is finished, then the mapped GLPI item task is set as "done". Start and end dates are set accordingly.
  • When a PM task is re-assigned, then the GLPI item task is re-assigned to the new technician.
  • When a task is 'to be claimed' (= it has been assigned to a group) then as soon as someone in this group claims the task, it is assigned to this user.
  • If GLPI notifications are enabled for GLPI item tasks, then notifications for Task Events are going to be sent.
Clone this wiki locally