From 5488ca210471b7f59a4de09726fd3acec08a749c Mon Sep 17 00:00:00 2001 From: Joost Verhoog Date: Mon, 20 Oct 2025 09:07:47 +0200 Subject: [PATCH 1/3] Introduce optional parameters --- .../integration-activities/call-external-action.md | 8 +++++++- .../integration-activities/call-external-action.md | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md index 252f1386f55..8162a218464 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md @@ -65,6 +65,12 @@ In the **Documentation** tab, you can find a **Summary** and a **Description**. The **Edit External Action Parameter Mapping** dialog allows you to set the value of the parameter you pass to an external action. You can either select a **Variable** from the dropdown field, or write a custom [microflow expression](/refguide/expressions/) that returns a value of the expected type. -Every parameter must have a value specified. When **Can be empty** is true, the selected variable or expression may evaluate to `empty`. When the value cannot be empty, the microflow will throw an error if the value evaluates to `empty`. +Every parameter must have a value specified unless the service indicates that the parameter is optional (with the `Org.OData.Core.V1.OptionalParameter` annotation). + +When the service indicates that a value cannot be empty (with `Nullable="false"`) then the microflow will throw an error if the value evaluates to `empty`. If you have selected a variable for an entity that has associations, you can select which associations you want to include in the arguments that you call the external action with. + +{{% alert color="info" %}} +The possibility to not specify a value for optional parameters was introduced in Studio Pro 11.4.0. +{{% /alert %}} diff --git a/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md b/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md index d2356c5ebac..87e9bfb911e 100644 --- a/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md +++ b/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md @@ -69,7 +69,7 @@ In the **Documentation** tab, you can find a **Summary** and a **Description**. The **Edit External Action Parameter Mapping** dialog allows you to set the value of the parameter you pass to an external action. You can either select a **Variable** from the dropdown field, or write a custom [microflow expression](/refguide10/expressions/) that returns a value of the expected type. -Every parameter must have a value specified. When **Can be empty** is true, the selected variable or expression may evaluate to `empty`. When the value cannot be empty, the microflow will throw an error if the value evaluates to `empty`. +Every parameter must have a value specified. When the service indicates that a value cannot be empty (with `Nullable="false"`) then the microflow will throw an error if the value evaluates to `empty`. If you have selected a variable for an entity that has associations, you can select which associations you want to include in the arguments that you call the external action with. From f518a090fdbef1b1f7f7d056f264756965e1aebb Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Mon, 20 Oct 2025 16:22:12 +0200 Subject: [PATCH 2/3] Small edit --- .../activities/integration-activities/call-external-action.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md index 8162a218464..0941a5e55f4 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md @@ -67,7 +67,7 @@ The **Edit External Action Parameter Mapping** dialog allows you to set the valu Every parameter must have a value specified unless the service indicates that the parameter is optional (with the `Org.OData.Core.V1.OptionalParameter` annotation). -When the service indicates that a value cannot be empty (with `Nullable="false"`) then the microflow will throw an error if the value evaluates to `empty`. +When the service indicates that a value cannot be empty (with `Nullable="false"`), the microflow will throw an error if the value evaluates to `empty`. If you have selected a variable for an entity that has associations, you can select which associations you want to include in the arguments that you call the external action with. From 0dee52fc8bb1085b60c1797a6af7d20cdd03c904 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Mon, 20 Oct 2025 16:22:37 +0200 Subject: [PATCH 3/3] Small edit --- .../activities/integration-activities/call-external-action.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md b/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md index 87e9bfb911e..b1d59a61171 100644 --- a/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md +++ b/content/en/docs/refguide10/modeling/application-logic/microflows-and-nanoflows/activities/integration-activities/call-external-action.md @@ -69,7 +69,7 @@ In the **Documentation** tab, you can find a **Summary** and a **Description**. The **Edit External Action Parameter Mapping** dialog allows you to set the value of the parameter you pass to an external action. You can either select a **Variable** from the dropdown field, or write a custom [microflow expression](/refguide10/expressions/) that returns a value of the expected type. -Every parameter must have a value specified. When the service indicates that a value cannot be empty (with `Nullable="false"`) then the microflow will throw an error if the value evaluates to `empty`. +Every parameter must have a value specified. When the service indicates that a value cannot be empty (with `Nullable="false"`), the microflow will throw an error if the value evaluates to `empty`. If you have selected a variable for an entity that has associations, you can select which associations you want to include in the arguments that you call the external action with.