Merge pull request mendix#9062 from EnasAbdelrazek/ufc-nf-mf-conversion-improvement

Document Nanoflow and microflow conversion improvement

Author: Yiyun333

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/_index.md

@@ -112,11 +112,27 @@ If you want to see what happens while a microflow is executing, you can use the
 
 ## Converting a Microflow to a Nanoflow {#convert-to-nanoflow}
 
-To convert a microflow to a nanoflow, you have two options. The first option is to right-click anywhere in the microflow editor and select **Convert to nanoflow**. Alternatively, in the **App Explorer**, right-click on the name of the microflow you want to convert, and select **Convert to nanoflow**.
+In Studio Pro 10.19 and below, you can use the **Convert to nanoflow** functionality to create a new nanoflow based on the original microflow. There are two ways to find this option:
+
+* Right-click anywhere in the microflow editor and click **Convert to nanoflow**. 
+* Alternatively, in the **App Explorer**, right-click on the name of the microflow you want to convert, and click **Convert to nanoflow**.
 
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/convert-to-nanoflow.PNG" alt="Convert to nanoflow" width="550px" class="no-border" >}}
 
-A new nanoflow is created and added to the same directory, and you can get consistency errors if there are actions that are not supported by nanoflows.
+Afterwards, a new nanoflow is created and added to the same directory, and you can get consistency errors if there are actions that are not supported by nanoflows.
+
+Starting from Studio Pro 10.20, there are two options available:
+
+* **Duplicate as nanoflow**: This option creates a new nanoflow based on the original microflow. This works the same as the **Convert to nanoflow** functionality in Studio Pro 10.19 and below.
+* **Convert to nanoflow**: This option removes the original microflow and replaces it with a new nanoflow. All possible usages throughout your app are updated and any non-replaceable usages remain as they are. When some usages cannot be replaced because they are not allowing nanoflows, a warning dialog appears. See below as an example:
+
+    {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/warning-dialog.png" alt="Conversion warning dialog" width="550px" >}}
+
+    In the warning dialog, you have the following options:
+
+    * **Convert**: The original microflow is removed, only replaceable usages are updated, and any non-replaceable usages remain as they are.
+    * **Find usages**: Stops the conversion and finds usages of the original microflow.
+    * **Cancel**: The conversion is cancelled and no changes are made.
 
 ## Canvas Interaction {#canvas-interaction}
 

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/_index.md

@@ -140,11 +140,27 @@ Nanoflows are executed in the context of the current user. Any operation for whi
 
 ## Converting a Nanoflow to a Microflow {#convert-to-microflow}
 
-To convert a nanoflow to a microflow, you have two options. The first option is to right-click anywhere in the nanoflow editor and select **Convert to microflow**. Alternatively, in the **App Explorer**, right-click on the name of the nanoflow you want to convert, and select **Convert to microflow**.
+In Studio Pro 10.19 and below, you can use the **Convert to microflow** functionality to create a new microflow based on the original nanoflow. There are two ways to find this option:
+
+* Right-click anywhere in the nanoflow editor and click **Convert to microflow**. 
+* Alternatively, in the **App Explorer**, right-click on the name of the nanoflow you want to convert, and click **Convert to microflow**.
 
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/convert-to-microflow.PNG" alt="Convert to microflow" width="550px" class="no-border" >}}
 
-A new microflow is created and added to the same directory, and you can get consistency errors if there are elements that are not supported by microflows.
+Afterwards, a new microflow is created and added to the same directory, and you can get consistency errors if there are elements that are not supported by microflows.
+
+Starting from Studio Pro 10.20, there are two options available:
+
+* **Duplicate as microflow**: This option creates a new microflow based on the original nanoflow. This works the same as the **Convert to microflow** functionality in Studio Pro 10.19 and below.
+* **Convert to microflow**: This option removes the original nanoflow and replaces it with a new microflow. All possible usages throughout your app are updated and any non-replaceable usages remain as they are. When some usages cannot be replaced because they are not allowing microflows, a warning dialog appears. See below as an example:
+
+    {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/warning-dialog.png" alt="Conversion warning dialog" width="550px" >}}
+
+    In the warning dialog, you have the following options:
+
+    * **Convert**: The original nanoflow is removed, only replaceable usages are updated, and any non-replaceable usages remain as they are.
+    * **Find usages**: Stops the conversion and finds usages of the original nanoflow.
+    * **Cancel**: The conversion is cancelled and no changes are made.
 
 ## Canvas Interaction