Business processes in 1C:Enterprise are intended to combine individual operations into chains of interrelated actions that lead to accomplishment of specific goals. For example, issuing an invoice, accepting a cash payment, and shipping goods from a warehouse can be combined into a Sale business process.
Such chains of interrelated operations within a business process are presented in the business process route map. A route map describes the logic of the business process and its entire lifecycle, from start to finish, in the form of a flowchart that displays a sequence of route points.
A route point reflects a stage in the lifecycle of a business process, normally involving the completion of a single automatic or manual operation.
Tasks in 1C:Enterprise allow you to keep a record of jobs sorted by performer, and reflect the progress of business processes through the flowchart. In addition to business processes, tasks can be created by other infobase objects or directly by users.
When a business process reaches any route point where actions of a specific performer are required, a task is generated (or multiple tasks for multiple performers). When a performer marks the task as executed, the business process automatically proceeds to the next route point in compliance with the flowchart. Thus, tasks are the driving force for business processes.
Specific business processes and their interconnection with tasks are described in the application documentation.
The general principles of working with business processes and tasks are similar to working with other objects (for example, documents and lists), therefore we will only cover the differences.