Process Diagram¶

A process diagram is a visualized model consisting of Tasks, Actions, Roles and Routes. For example, a simple expense process is modeled as follows;

Leave Request
Defines the start task of the process. Employee can save or submit a leave request.

Manager Approval
Defines the first approval task of the process. Manager can confirm or reject the request. If rejected, the process is routed back to the employee.

HR Approval
Defines the second approval task of the process. Human Resources can confirm or reject the request, and if HR confirms the request, the confirmed request is recorded in the HR database, else if rejected, the process is routed back to the manager.

Inform Employee
Defines the inform employee task of the process. Employee can select OK and finish the process.

Diagram Language¶

BPMN or similar notations generally contain technical terms like "if", "split", and "explicit join" activities and require some skills to understand diagram. Emakin uses it's own process notation to describe processes to achieve the understanding of the processes by everyone without any education or skills needed.

According to the diagram above:

• Green box identifies the start (initiator) task of the pool.

• Orange boxes identify the intermediate task of the pool.

• Each gray box which is connected to the tasks, identifies the action as a result of a task that assigned user can select.

• Lines between actions and tasks identify the routes to the next task in the process. If no route is found process is terminated with selected action.

• Pools

  • Instance Opening Script
  • Instance Termination Script
  • Instance Closing Script
  • Variables
• Tasks
  • Task Prework Script
  • Task Postwork Script
  • Normal Tasks
  • Task Scheduling
  • Module Tasks
• Actions
• Roles
• Templates
• Forms
• Routes