Transactions when OFF is specified in both compatibility with the business process status and compatibility with the invoke service activity status

This subsection describes transactions if you specify OFF for both compatibility with the business process status (bp-status-compatible) and compatibility with the invoke service activity status (bp-invoke-status-compatible) in the HCSC server setup definition.

The following describes the operation if you specify OFF for compatibility with the business process status and compatibility with the invoke service activity status.

When processing of the invoke service activity starts, Executing is set in the status of the activity, and then the transaction terminates.
When processing of the invoke service activity finishes, Completed is set in the status of the activity, and the transaction does not terminate.
If an exception occurs during execution of the invoke service activity of the business process, Error is set in the status of the process instance and the invoke service activity, and then the transaction terminates.

Note that the operation is the same for synchronization and asynchronous communication models.

Organization of this subsection: (1) If two invoke service activities are arranged; (2) If a data transformation activity exists after an invoke service activity

(1) If two invoke service activities are arranged

If processing continues successfully: The transaction is committed immediately before the message send process of each invoke service activity, and a new transaction starts.; The following figure shows the transaction scope when processing continues successfully during the service invocation.; Figure 3-34 Transaction scope when processing continues successfully

If an exception occurs: If processing of service invocation 2 results in an error because of an exception, a rollback occurs up to the point where the transaction was committed (Reception: Completed, Service invocation 1: Completed, Service invocation 2: Executing). Then, Error is set in the status of the process instance and invoke service activity, and the transaction is committed.; The following figure shows the transaction scope if an exception occurs during the service invocation.; Figure 3-35 Transaction scope if an exception occurs

(2) If a data transformation activity exists after an invoke service activity

If processing continues successfully: The transaction is committed immediately before the message send process of each invoke service activity, and a new transaction starts.; Note that the transaction is not committed in the data transformation activity. This applies even for an activity other than those shown in Table 3-7 Timings for the start and commit of transactions.; The following figure shows the transaction scope when processing continues normally in the presence of an activity such as data transformation.; Figure 3-36 Transaction scope when processing continues successfully (when activities such as data transformation exist after service invocation)

If an exception occurs (when activities such as data transformation exist after service invocation): If an error occurs in the data transformation process after service invocation 1, a rollback occurs up to the point where the transaction was committed (Reception: Completed, Service invocation 1: Executing).; The following figure shows the transaction scope if an exception occurs in the presence of an activity, such as data transformation, after service invocation.; Figure 3-37 Transaction scope if an exception occurs (when activities such as data transformation exist after service invocation)

3.4.3 Transactions when OFF is specified in both compatibility with the business process status and compatibility with the invoke service activity status

(1) If two invoke service activities are arranged

(2) If a data transformation activity exists after an invoke service activity