While actions can be complex and comprehensive

[jarinislamfatema]

In some other notations, “agree on a deal” or some other complex actions can be considered as tasks. But this is only possible in those notations where such complex tasks can be subsequently decomposed. There is no such possibility in BPMN. Therefore, here the task must be the simplest action. In this notation there are sub-processes (Sub-Process) or sub-tasks (Sub-Task). We will consider these possibilities later. Here and now I am talking specifically about tasks. Tasks can be as simple and specific as possible. For example, you are offered the option "Conducting an inventory of the warehouse" as a description of the action.

It is not enough to change the verb form to "Take inventory list of honduras whatsapp phone numbers of the warehouse", you need to divide this complex action into parts and build a sequence. Assign actions to performers After you have described the tasks, you need to decide who will perform them. At this stage, it is worth assigning performers in advance, for example, with a simple pencil on paper. In fact, you cannot yet 100% determine who exactly will perform this or that action. Some performers are obvious, others may change based on the results of work on the business process. For example, now a purchase order is approved by a buyer.

In the future, we may decide that if the amount of goods exceeds a certain threshold, the final approval is performed by the manager. As a result, for large orders, the performer for the “approval” task will change. These tasks will already be what is called a task, i.e. tasks in BPMN. In addition, it is necessary to make a list of performers, it will be needed when working in the notation. Calculate the finals of the process The process can be completed in several cases. This can be a successful result, in which all stages are completed and the result is achieved.