Review: Reorganize the structure

Author: alihcsumer

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/return-value-mapping.md

@@ -7,34 +7,72 @@ weight: 60
 
 ## Introduction
 
-Pages and snippets can use [return values](/refguide/end-event/#return-value) when calling microflows or nanoflows by specifying a return value mapping. This feature enhances microflow and nanoflow reusability by allowing pages to update local values based on flow return values without needing to pass objects containing those attributes to the flow. 
+Pages and snippets can use [return values](/refguide/end-event/#return-value) when calling microflows or nanoflows by specifying a return value mapping. This feature enhances microflow and nanoflow reusability by allowing pages to decide how to use return values. Previously, modifying values on the page from a microflow or nanoflow required an additional entity passed as a parameter, resulting in many page-specific variations of the same logic.
 
 Return values can be mapped to available variables on the page or snippet. Both primitive and object return value types are supported. Using an expression, the return value can be transformed as needed before assignment.
 
+You can add more than one return value mapping to the same flow call. This is particularly useful when assigning multiple computed values to different variables from the same return value.
+
 {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/parameter/return-value-mapping-list.png" width="500px" class="no-border" >}}
 
-## Primitive Return Values
+## Supported Return Values
+
+Return value mapping supports both primitive values and objects from the microflow or nanoflow return value.
 
-For primitive return values (such as strings, booleans, integers, decimals, or enumerations), the value can be assigned to any matching attribute of available objects on the page, or to variables and parameters of pages or snippets. The target must have a compatible data type with the return value.
+### Supported Primitive Types
 
-## Object Return Values
+The following primitive types can be mapped directly:
 
-When a microflow or nanoflow returns an object, you can specify a return value mapping using one or more attributes of that object. This capability makes it possible to dynamically update multiple attributes, variables, and parameters with the return value of a single flow.
+* Boolean
+* Date and time
+* Decimal
+* Enumeration
+* Integer/Long
+* String
 
-To use multiple attributes from a returned object, add more than one return value mapping to the same flow call. This is particularly useful when assigning multiple computed values to different variables from the same return value.
+### Object Attributes
 
-## Mapping Return Values from a Page
+When a microflow or nanoflow returns an object, you can select specific attributes from that object. This allows you to extract individual values from the returned object without needing to work with the entire object on the page.
 
-When calling a microflow or nanoflow action, you can map return values in two primary ways.
+{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/parameter/variable-return-value-mapping.png" width="500px" class="no-border" >}}
 
-### Variable Return Value Mappings 
+### Lists Not Supported
 
-Variable return value mappings are used to map values returned by the microflow or nanoflow directly. When the flow returns an object, you can select specific attributes from that object to assign to variables on the page or snippet.
+Return value mapping does not support list return values. If your microflow or nanoflow returns a list, you cannot use return value mapping to capture it. In such cases, consider using a different approach, such as passing an object as a parameter or using the list directly in a data source.
 
-{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/parameter/variable-return-value-mapping.png" width="500px" class="no-border" >}}
+## Transforming Return Values
+
+You can use expressions to transform return values before they are assigned. In the expression, the return value is available as `$ActionReturnValue`.
+
+When the microflow or nanoflow returns an object, you can access attributes using `$ActionReturnValue/AttributeName`. This allows you to apply transformations to attributes, before assigning the value.
+
+{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/parameter/expression-return-value-mapping.png" width="500px" class="no-border" >}}
+
+**Example:**
+
+If a microflow returns an **Order** object with a **TotalAmount** attribute (Decimal), you can format it as currency before assigning it to a string page variable:
+
+```
+formatDecimal($ActionReturnValue/TotalAmount, '$#,##0.00')
+```
+
+## Page Variable Assignment
+
+Return values can be assigned to various targets available on the page or snippet.
+
+### Available Targets
+
+The following targets are available for return value mapping:
+
+* **Page and snippet variables** – Variables defined on the current page or snippet
+* **Page and snippet parameters** – Parameters of the current page or snippet
+* **Attributes of objects on the page** – Attributes of objects available in data views or other data containers on the page
 
-### Expression-Based Return Value Mappings 
+### Type Matching
 
-Both primitive values and object attributes can be mapped using expressions. This method allows you to use functions within the expression to modify the return value before it is assigned.
+The target variable or attribute must have a compatible data type with the return value. When using expressions, the result type of the expression must match the target type.
 
-{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/parameter/expression-return-value-mapping.png" width="500px" class="no-border" >}}
+For example:
+* A decimal return value can be assigned directly to a decimal page variable
+* A decimal return value can be transformed with an expression like `formatDecimal($ActionReturnValue, '#,##0.00')` and assigned to a string page variable
+* An object attribute can be extracted and assigned to a matching primitive variable