Suggest transaction boundaries within a business process
Transactional behavior of business processes
Business processes are executed as part of transactions. The navigation of a business process can span multiple transactions in the case of long-running processes, or happen as part of one transaction in the case of microflows. Such navigation transactions can be triggered by external requests, internal messages, or responses from asynchronous services. When a transaction starts, the required activities are performed according to the process definitions. Invoked services can participate in the transaction.
-
Microflowsrun under a single transaction in a short period of time.
-
Long-running business processesrun in a series of chained transactions over days, months, or even years. Long-running processes can be optimized with respect to transaction boundaries.
-
Commit beforeguarantees that the activity runs in a new transaction.
-
Commit afterguarantees that the current transaction is committed after executing the activity.
-
Requires ownguarantees that the activity runs in a new transaction and the current transaction is committed after executing the activity.
-
Participatesbehavior states that the activity runs within an existing transaction, if one is available.
Setting up a process as long-running
Setting up Human Task transaction behaviour
Related links
-
Long running processes and microflows (Guided Tour)
No comments:
Post a Comment