Skip to content

Commit 1e12568

Browse files
daviburgecfan
andauthored
Update articles/logic-apps/connectors/sap.md
Co-authored-by: Esther Fan <[email protected]>
1 parent cc81618 commit 1e12568

File tree

1 file changed

+3
-1
lines changed
  • articles/logic-apps/connectors

1 file changed

+3
-1
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,9 @@ SAP upgraded their .NET connector (NCo) to version 3.1, which changed the way th
167167

168168
* For a Standard workflow in single-tenant Azure Logic Apps, see [Single-tenant prerequisites](#single-tenant-prerequisites).
169169

170-
* By default, the SAP built-in connector operations are *stateless*. To run these operations in stateful mode, see [Enable stateful mode for stateless built-in connectors](/azure/connectors/enable-stateful-affinity-built-in-connectors). Stateful communications must remain in the same processing instance as the workflow for the following kinds of operations:
170+
* By default, the SAP built-in connector operations are *stateless*. To run these operations in stateful mode, see [Enable stateful mode for stateless built-in connectors](/azure/connectors/enable-stateful-affinity-built-in-connectors).
171+
172+
Stateful communications must stay with the same workflow instance during processing. A Standard logic app can use [scale out](/azure/connectors/enable-stateful-affinity-built-in-connectors#prevent-context-loss-during-resource-scale-in-events) to distribute the workload over multiple workflow instances when needed. This requirement applies to the following kinds of operations:
171173

172174
* All actions that specify a **Session ID** value, such as **[BAPI] Commit transaction**.
173175

0 commit comments

Comments
 (0)