diff --git a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md index a22673df3d3..239d3bbd449 100644 --- a/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md +++ b/content/en/docs/apidocs-mxsdk/mxsdk/sdk-refguide/understanding-the-metamodel/microflows-metamodel.md @@ -128,7 +128,7 @@ A retrieve action is either an association-based retrieve or a database-based re | Studio Pro Guide | Model SDK API docs | | --- | --- | -| [Retrieve](/refguide/retrieve/) |[RetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.retrievesource.html) | +| [Retrieve object(s)](/refguide/retrieve-objects/) |[RetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.retrievesource.html) | | [XPath](/refguide/xpath/) constraints |[AssociationRetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.associationretrievesource.html) | | |[DatabaseRetrieveSource](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.databaseretrievesource.html) | | |[Range](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.range.html), [ConstantRange](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.constantrange.html) and [CustomRange](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.customrange.html) | @@ -144,7 +144,7 @@ Microflows can call other microflows by defining a mapping of expressions to par | Studio Pro Guide | Model SDK API docs | | --- | --- | -| [Microflow Call](/refguide/microflow-call/) |[MicroflowCallAction](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.microflowcallaction.html) | +| [Call Microflow](/refguide/microflow-call/) |[MicroflowCallAction](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.microflowcallaction.html) | | |[MicroflowCall](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.microflowcall.html) | | |[MicroflowCallParameterMapping](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.microflowcallparametermapping.html) | @@ -315,7 +315,7 @@ Java action calls point to a specific Java action and have a parameter mapping w | Studio Pro Guide | Model SDK API docs | | --- | --- | -| [Java Action Call](/refguide/java-action-call/) |[JavaAction](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/javaactions.javaaction.html) | +| [Call Java Action](/refguide/call-java-action/) |[JavaAction](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/javaactions.javaaction.html) | | |[JavaActionParameter](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/javaactions.javaactionparameter.html) | | |[JavaActionCallAction](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.javaactioncallaction.html) | | |[JavaActionParameterMapping](https://apidocs.rnd.mendix.com/modelsdk/latest/classes/microflows.javaactionparametermapping.html) | diff --git a/content/en/docs/howto/data-models/denormalize-data-to-improve-performance.md b/content/en/docs/howto/data-models/denormalize-data-to-improve-performance.md index e90fdc1663d..bf88027ecae 100644 --- a/content/en/docs/howto/data-models/denormalize-data-to-improve-performance.md +++ b/content/en/docs/howto/data-models/denormalize-data-to-improve-performance.md @@ -74,7 +74,7 @@ Now the application is ready to store redundant data, but you still need to keep {{< figure src="/attachments/howto/data-models/denormalize-data-to-improve-performance/18582163.png" class="no-border" >}} -8. Drag a **Retrieve** activity from the toolbox to the line between the start and end event on the microflow, which will insert a new retrieve activity: +8. Drag a **Retrieve object(s)** activity from the toolbox to the line between the start and end event on the microflow, which will insert a new retrieve object(s) activity: {{< figure src="/attachments/howto/data-models/denormalize-data-to-improve-performance/18582164.png" class="no-border" >}} @@ -96,7 +96,7 @@ Now the application is ready to store redundant data, but you still need to keep {{< figure src="/attachments/howto/data-models/denormalize-data-to-improve-performance/18582159.png" class="no-border" >}} -12. Insert another retrieve activity (as you did in step #8), double-click it to open its properties on the **Retrieve** dialog box, and do the following: +12. Insert another Retrieve object(s) activity (as you did in step #8), double-click it to open its properties on the **Edit Retrieve Object(s)** dialog box, and do the following: * Select **From Database** as **Source** * Click **Select...** to open the entity selector diff --git a/content/en/docs/howto/extensibility/best-practices-javascript-actions.md b/content/en/docs/howto/extensibility/best-practices-javascript-actions.md index de3f20178d6..6299581f069 100644 --- a/content/en/docs/howto/extensibility/best-practices-javascript-actions.md +++ b/content/en/docs/howto/extensibility/best-practices-javascript-actions.md @@ -381,7 +381,7 @@ Consider these additional technical suggestions for best API practices: ### Exposing JavaScript Actions -JavaScript Actions can be used in a nanoflow with a JavaScript action call activity. It is also possible to expose the actions in the activity list. This will make it easier for developers to find the actions. It is recommended to expose only the actions that will be reused often. +JavaScript Actions can be used in a nanoflow with a Call JavaScript action activity. It is also possible to expose the actions in the activity list. This will make it easier for developers to find the actions. It is recommended to expose only the actions that will be reused often. Use **Category** to group actions, **Icon** and **Image** to give the exposed nanoflow action easy recognition inside the nanoflow: diff --git a/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-actions.md b/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-actions.md index 57b07675c65..9861231bfea 100644 --- a/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-actions.md +++ b/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-actions.md @@ -119,7 +119,7 @@ To create a JavaScript action that can synthesize text to speech, follow these s } ``` -9. You have just implemented your first JavaScript action! You can start using the action in your nanoflows by adding a **JavaScript action call** and selecting the newly created **SpeechToText** action: +9. You have just implemented your first JavaScript action! You can start using the action in your nanoflows by adding a **Call JavaScript action** and selecting the newly created **SpeechToText** action: {{< figure src="/attachments/howto/extensibility/build-javascript-actions/write-javascript-actions/selectjsactioncalldetail.png" alt="select text to speech action" class="no-border" >}} diff --git a/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-github.md b/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-github.md index d250dea8696..321739dbbea 100644 --- a/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-github.md +++ b/content/en/docs/howto/extensibility/build-javascript-actions/write-javascript-github.md @@ -244,7 +244,7 @@ To create a JavaScript action that can search for users on GitHub, follow the st } ``` -16. You have just implemented an advanced JavaScript action! Start using the action in your nanoflows by adding a **JavaScript action call**, and then selecting the newly created **SearchGitHubUsers** action: +16. You have just implemented an advanced JavaScript action! Start using the action in your nanoflows by adding a **Call JavaScript action**, and then selecting the newly created **SearchGitHubUsers** action: {{< figure src="/attachments/howto/extensibility/build-javascript-actions/write-javascript-github/select-searchgithub-users.png" alt="select search GitHub users" class="no-border" >}} diff --git a/content/en/docs/marketplace/genai/how-to/create-single-agent.md b/content/en/docs/marketplace/genai/how-to/create-single-agent.md index 1f29c95d36d..beaf27bbff0 100644 --- a/content/en/docs/marketplace/genai/how-to/create-single-agent.md +++ b/content/en/docs/marketplace/genai/how-to/create-single-agent.md @@ -103,7 +103,7 @@ Mendix ticket data needs to be ingested into the knowledge base. You can find a 5. In `Tickets_CreateDataset`, open the `Retrieve Ticket from database` action and reselect the entity `Ticket`. Open the `Import from JSON` action and select the **IM_Ticket**. 6. In the `ACT_TicketList_LoadAllIntoKnowledgeBase`: - * Edit the first retrieve action to retrieve objects from your new entity `Ticket`. + * Edit the first retrieve object(s) activity to retrieve objects from your new entity `Ticket`. * In the loop, delete the second action that adds metadata to the `MetadataCollection`. * In the last action of the loop `Chunks: Add KnowledgeBaseChunk to ChunkCollection` keep the **Human readable ID** field empty. @@ -154,7 +154,7 @@ The final result for the function microflows used in this document can be found 1. Create a new microflow named `Ticket_GetNumberOfTicketsInStatus`. Add a *String* input parameter called `TicketStatus`. -2. The model can now pass a status string to the microflow, but first convert the input into an enumeration. To achieve this, add a `Microflow call` action and create a new microflow named `Ticket_ParseStatus`. The input should be the same (*String* input `TicketStatus`). +2. The model can now pass a status string to the microflow, but first convert the input into an enumeration. To achieve this, add a `Call Microflow` activity and create a new microflow named `Ticket_ParseStatus`. The input should be the same (*String* input `TicketStatus`). 3. Inside of the sub-microflow, add a decision for each enumeration value and return the enumeration value in the **End event**. For example, the *Closed* value can be checked like this: diff --git a/content/en/docs/marketplace/partner-solutions/apd/ig/ig-one/ig-one-uninstall-steps.md b/content/en/docs/marketplace/partner-solutions/apd/ig/ig-one/ig-one-uninstall-steps.md index f3dee118d50..034a9a13d05 100644 --- a/content/en/docs/marketplace/partner-solutions/apd/ig/ig-one/ig-one-uninstall-steps.md +++ b/content/en/docs/marketplace/partner-solutions/apd/ig/ig-one/ig-one-uninstall-steps.md @@ -49,8 +49,8 @@ Delete the APM Tools item that calls "APMAgent/USE_ME/IVK_OpenConsole" from navi ## Optional: Revert After Startup and Before Shutdown -Remove the microflow call action to APMAgent\USE_ME\AfterStartup from an after startup microflow. This feature is runtime configurable and by default none of the tools are started. -Remove the microflow call action to APMAgent\USE_ME\BeforeShutdown from a before shutdown microflow. +Remove the microflow call activity to APMAgent\USE_ME\AfterStartup from an after startup microflow. This feature is runtime configurable and by default none of the tools are started. +Remove the microflow call activity to APMAgent\USE_ME\BeforeShutdown from a before shutdown microflow. You can find the AfterStartup and BeforeShutdown microflows in the project settings. {{< figure src="/attachments/appstore/partner-solutions/apd/ig/ig-one/ig-one-uninstall-steps/Revert_After_Startup.png" class="no-border" >}} diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-bedrock.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-bedrock.md index 665d338137c..2aa6d027199 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-bedrock.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-bedrock.md @@ -135,8 +135,8 @@ For operations that do not depend on the GenAI Commons, you can take a different 2. Drag the one you would like to use to the beginning of your microflow. 3. Double-click the microflow action to configure the required parameters and provide a value for the AWS Region. For the **ListFoundationModels** parameter, provide the `ListFoundationModelsRequest` created in step 3. 9. The `ListFoundationModelsResponse` object is returned by the **ListFoundationModels** activity. -10. From the **Toolbox**, drag a **Retrieve** activity to your microflow and place it after the **ListFoundationModels** activity. -11. Double-click the **Retrieve** activity and make sure **By Association** is selected. +10. From the **Toolbox**, drag a **Retrieve object(s)** activity to your microflow and place it after the **ListFoundationModels** activity. +11. Double-click the **Retrieve object(s)** activity and make sure **By Association** is selected. 12. Select the **FoundationModelSummary_ListFoundationModelsResponse** association, which will return a list of the type **FoundationModelSummary**. 13. To further use the response information, you can create an implementation module with copies of the `ListFoundationModelsResponse` and `ModelSummary` Entities. This way, you can use your custom user roles and access rules for those entities and keep them when updating the connector. @@ -152,7 +152,7 @@ To build a simple microflow that uses the ChatCompletions operation to send a si 1. Make sure that you [synced models](#sync-models) before running the microflow in the app. 2. Create a new microflow and name it, for example, *AmazonBedrockChatCompletions*. -3. Add a **Microflow call** from the **Toolbox** and choose microflow *AmazonBedrockConnector.BedrockDeployedModel_Get* +3. Add a **Call microflow** activity from the **Toolbox** and choose microflow *AmazonBedrockConnector.BedrockDeployedModel_Get* 4. Double-click it to configure its parameters. 1. For the **ModelID** parameter, enter the model id of the LLM you want to send a message to. The model id of Claude 3.5 Sonnet is *anthropic.claude-3-5-sonnet-20240620-v1:0*. 2. Click **OK**. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-rekognition.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-rekognition.md index f555c3e0d1d..6a22f001ba4 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-rekognition.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/amazon-rekognition.md @@ -74,9 +74,9 @@ After you configure the authentication profile for Amazon Rekognition, you can i 2. Drag the one you would like to use to the beginning of your microflow. 3. Double-click the microflow action to configure the required parameters and provide a value for the AWS Region. 8. The `DetectLabelResponse` object is returned by the **DetectLabels** activity. -9. In the **Toolbox** pane, search for the **Retrieve** activity and drag it onto the microflow work area. -10. Position the **Retrieve** activity between the **DetectLabels** activity and the microflow end event. -11. Double-click the **Retrieve** activity. +9. In the **Toolbox** pane, search for the **Retrieve object(s)** activity and drag it onto the microflow work area. +10. Position the **Retrieve object(s)** activity between the **DetectLabels** activity and the microflow end event. +11. Double-click the **Retrieve object(s)** activity. 12. In the **Select Association** dialog box, in the **Association** section, click **Select**, and then select **DetectLabels** as the association. 13. Click **OK**. 14. Configure a method for triggering the **ACT_DetectLabels** microflow. For example, you can trigger a Microflow by associating it with a custom button on a page in your app. For an example of how this can be implemented, see [Creating a Custom Save Button with a Microflow](/refguide/creating-a-custom-save-button/). diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-dynamodb.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-dynamodb.md index 1123b070d94..6e8b80dfad7 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-dynamodb.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-dynamodb.md @@ -105,12 +105,12 @@ After you configure the authentication profile for Amazon DynamoDB, you can impl * Click **Edit parameter value**. * Edit the **CreateBucketRequest** parameter and let it auto-fill. -23. In the **Toolbox** pane, search for the **Retrieve** activity and drag it onto the microflow area. -24. Position the **Retrieve** activity between the **ListTables** activity and the microflow end event. +23. In the **Toolbox** pane, search for the **Retrieve object(s)** activity and drag it onto the microflow area. +24. Position the **Retrieve object(s)** activity between the **ListTables** activity and the microflow end event. - {{< figure src="/attachments/appstore/platform-supported-content/modules/aws-dynamodb/microflow.png" alt="The microflow with the Retrieve activity added" class="no-border" >}} + {{< figure src="/attachments/appstore/platform-supported-content/modules/aws-dynamodb/microflow.png" alt="The microflow with the Retrieve object(s) activity added" class="no-border" >}} -25. Double-click the **Retrieve** activity. +25. Double-click the **Retrieve object(s)** activity. 26. In the **Association** section, click **Select**. 27. In the **Select Association** dialog box, expand the **Variable** item, and then select **ListTablesResponse** as the association. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-sitewise.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-sitewise.md index 69711dd932b..78cba80a032 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-sitewise.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-sitewise.md @@ -60,9 +60,9 @@ After you configure the authentication profile for AWS IoT SiteWise, you can imp 6. Double-click the **ListAssetModels** microflow activity to configure the required parameters. 7. In the **Edit parameters** section, edit the **ENUM_Region** parameter, and provide a value by using a variable or an expression. 8. Click **OK**. -9. In the **Toolbox** pane, search for the **Retrieve** activity and drag it onto the microflow area. -10. Position the **Retrieve** activity between the **ListAssetModels** activity and the microflow end event. -11. Double-click the **Retrieve** activity. +9. In the **Toolbox** pane, search for the **Retrieve object(s)** activity and drag it onto the microflow area. +10. Position the **Retrieve object(s)** activity between the **ListAssetModels** activity and the microflow end event. +11. Double-click the **Retrieve object(s)** activity. 12. In the **Select Association** dialog box, in the **Association** section, click **Select**, and then select **ListAssetModels** as the association. 13. Click **OK**. 14. Configure a method for triggering the **ACT_ListAssetModels** microflow. For example, you can trigger a microflow by associating it with a custom button on a page in your app. For an example of how this can be implemented, see [Creating a Custom Save Button with a Microflow](/refguide/creating-a-custom-save-button/). diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-twinmaker.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-twinmaker.md index 2b447a430db..7c0f3601b1a 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-twinmaker.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-iot-twinmaker.md @@ -84,18 +84,18 @@ After you configure the authentication profile for AWS IoT TwinMaker, you can im 18. Double-click the **ListWorkspaces** activity. 19. Click **Edit parameter value**, edit the **ListWorkspacesRequest** parameter, and let it auto-fill. 20. In the **Object name** field, enter *ListWorkspacesResponse*, and then click **OK**. -21. In the **Toolbox** pane, search for the **Retrieve** activity and drag it onto the microflow area. -22. Position the **Retrieve** activity between the **ListWorkspaces** activity and the microflow end event. +21. In the **Toolbox** pane, search for the **Retrieve object(s)** activity and drag it onto the microflow area. +22. Position the **Retrieve object(s)** activity between the **ListWorkspaces** activity and the microflow end event. - {{< figure src="/attachments/appstore/platform-supported-content/modules/aws-iot-twinmaker/microflow.png" alt="The microflow with the Retrieve activity added" class="no-border" >}} + {{< figure src="/attachments/appstore/platform-supported-content/modules/aws-iot-twinmaker/microflow.png" alt="The microflow with the Retrieve object(s) activity added" class="no-border" >}} -23. Double-click the **Retrieve** activity. +23. Double-click the **Retrieve object(s)** activity. 24. In the **Association** section, click **Select**, and then select **ListWorkspacesResponse_WorkspaceSummary** as the association. {{< figure src="/attachments/appstore/platform-supported-content/modules/aws-iot-twinmaker/selectassociation.png" alt="Selecting the association" class="no-border" >}} 25. In the **List name** field, enter *WorkspaceSummaryList*, and then click **OK**. -26. In the **Toolbox** pane, search for the **Create List** activity, drag it onto the microflow area, and then position it after the **Retrieve** activity. +26. In the **Toolbox** pane, search for the **Create List** activity, drag it onto the microflow area, and then position it after the **Retrieve object(s)** activity. 27. Double-click the **Create List** activity. 28. In the **Action** section, click **Select**, and then select **{module name}.MyWorkspace** as the action. 29. In the **List name** field, enter *MyWorkspaceList*, and then click **OK**. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-sqs.md b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-sqs.md index 5a616bd8a40..3cfcf27e149 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-sqs.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/aws/aws-sqs.md @@ -64,9 +64,9 @@ For example, to list all existing Amazon SQS subscriptions, implement the **List 14. Set the value of the **Region** parameter in the same way as for the **GetStaticCredentials** or **GetTemporaryCredentials** activity. 15. Click **Edit parameter value**, edit the **ListQueuesRequest** parameter, and let it auto-fill. 16. Click **Edit parameter value**, edit the **Credentials** parameter, and let it auto-fill. -17. In the **Toolbox** pane, search for the **Retrieve** activity and drag it onto the microflow area. -18. Position the **Retrieve** activity between the **ListQueue** activity and the microflow end event. -19. Double-click the **Retrieve** activity. +17. In the **Toolbox** pane, search for the **Retrieve object(s)** activity and drag it onto the microflow area. +18. Position the **Retrieve object(s)** activity between the **ListQueue** activity and the microflow end event. +19. Double-click the **Retrieve object(s)** activity. 20. In the **Select Association** dialog box, in the **Association** section, click **Select**, and then under **ListQueueResponse** select *ListQueue_ListQueuesResponse* as the association. 21. Click **OK**. 22. Configure a method for triggering the **ACT_ListQueues** microflow. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/community-commons-function-library.md b/content/en/docs/marketplace/platform-supported-content/modules/community-commons-function-library.md index 933f76d55a1..cde6178c3d1 100644 --- a/content/en/docs/marketplace/platform-supported-content/modules/community-commons-function-library.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/community-commons-function-library.md @@ -11,7 +11,7 @@ The [Community Commons](https://marketplace.mendix.com/link/component/170/) modu ## Usage -All the functions in this package can be invoked using a [Java action call](/refguide/java-action-call/) in a microflow or from your own Java code by calling `communitycommons..;` (for example, `communitycommons.StringUtils.hash("Mendix", 20);`). +All the functions in this package can be invoked using a [Call Java action](/refguide/call-java-action/) in a microflow or from your own Java code by calling `communitycommons..;` (for example, `communitycommons.StringUtils.hash("Mendix", 20);`). The module contains one constant: `CommunityCommons.MergeMultiplePdfs_MaxAtOnce`. This is used in the `MergeMultiplePdfs` Java action to restrict the number of PDFs processed at the same time. The default restriction is 10 files at once for Mendix Cloud compatibility. If you need to merge more than 10 files, increase the number here. Setting the value to `<= 0` means unlimited. diff --git a/content/en/docs/refguide/java-programming/extending-your-application-with-custom-java.md b/content/en/docs/refguide/java-programming/extending-your-application-with-custom-java.md index 0b0e7402d10..912ab8fe957 100644 --- a/content/en/docs/refguide/java-programming/extending-your-application-with-custom-java.md +++ b/content/en/docs/refguide/java-programming/extending-your-application-with-custom-java.md @@ -186,10 +186,10 @@ The example skips many features you would want to add to a real app, but is desi ### XPath in Microflow -Firstly, a reminder of how this XPath could be implemented in a Retrieve activity. You can use this XPath in a Retrieve activity in a microflow using the following steps: +Firstly, a reminder of how this XPath could be implemented in a Retrieve object(s) activity. You can use this XPath in a Retrieve object(s) activity in a microflow using the following steps: 1. Create a new microflow in the **Products** module and name it *ListWithRetrieve*. -2. Add a **Retrieve** activity and configure it as follows: +2. Add a **Retrieve object(s)** activity and configure it as follows: * Source: From database * Entity: Products.Category @@ -200,7 +200,7 @@ Firstly, a reminder of how this XPath could be implemented in a Retrieve activit This will retrieve a category for us to use in the XPath. -3. Add a second **Retrieve** activity and configure it as follows: +3. Add a second **Retrieve object(s)** activity and configure it as follows: * Source: From database * Entity: Products.Product @@ -289,7 +289,7 @@ To use this same XPath in a Java action called from a microflow, perform the fol 6. Select **File** > **Save** to save the Java action in Eclipse. 7. In Studio Pro, **Duplicate** the **ListWithRetrieve** microflow you created in the previous section and **Rename** it *ListWithJavaAction*. 8. Edit the **ListWithJavaAction** microflow. -9. Delete the second **Retrieve** activity. +9. Delete the second **Retrieve object(s)** activity. 10. Drag the **findProductByNameAndCategory** Java action to the end of the microflow 11. Configure the inputs of the **findProductByNameAndCategory** Java action as follows: diff --git a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md index f6fe49e9b33..e14e6c78bb3 100644 --- a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md +++ b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md @@ -15,7 +15,7 @@ To ensure the best user experience for your Mendix application, follow these bes * Synchronize large files or images using selective synchronization * Use an `isDeleted` Boolean attribute for delete functionality so that conflicts can be handled correctly on the server * Use before- and after-commit microflows to pre- or post-process data -* Use a [microflow call](/refguide/microflow-call/) in your nanoflows to perform additional server-side logic such as retrieving data from a REST service, or accessing and using complex logic such as Java actions +* Use a [Call microflow](/refguide/microflow-call/) activity in your nanoflows to perform additional server-side logic such as retrieving data from a REST service, or accessing and using complex logic such as Java actions * Help your user remember to synchronize their data so it is processed as soon as possible: you can check for connectivity and automatically synchronize in the nanoflow that commits your object, or remind a user to synchronize while using a notification or before signing out to ensure no data is lost ## Preventing Synchronization Issues @@ -41,7 +41,7 @@ Mendix helps developers build rich offline-first apps. However, there are some l ### Microflows {#microflows} -Microflows can be called from offline apps by using [microflow call](/refguide/microflow-call/) action in your nanoflows to perform logic on the server. However, it works a bit different from when used in online profiles, these differences are explained below: +Microflows can be called from offline apps by using [Call microflow](/refguide/microflow-call/) activities in your nanoflows to perform logic on the server. However, it works a bit different from when used in online profiles, these differences are explained below: #### Microflow Arguments Type diff --git a/content/en/docs/refguide/mobile/using-mobile-capabilities/local-notifications/local-notif-data.md b/content/en/docs/refguide/mobile/using-mobile-capabilities/local-notifications/local-notif-data.md index 8dc8b9bc19a..2565fbb1884 100644 --- a/content/en/docs/refguide/mobile/using-mobile-capabilities/local-notifications/local-notif-data.md +++ b/content/en/docs/refguide/mobile/using-mobile-capabilities/local-notifications/local-notif-data.md @@ -116,11 +116,12 @@ To make your page, do the following: Next you will learn how to pass data to pages after you have tapped a notification. First, make a nanoflow: 1. Create a nanoflow named *ACT_PassGUIDToNotification*. -2. Add a retrieve action to your nanoflow, set **Source** to **From Database**, and set **Range** to **First**. Click **Entity** > **Select** and select the **TestEntity**. In **Object name** type *FirstTestEntityObject*. Then click **OK**. This will be the object that gets the GUID: +2. Add a **Retrieve object(s)** activity to your nanoflow, set **Source** to **From database**, and set **Range** to **First**. Click **Entity** > **Select** and select the **TestEntity**. In **Object name** type *FirstTestEntityObject*. Then click **OK**. This will be the object that gets the GUID: + {{< figure src="/attachments/howto/mobile/native-mobile/implementation/notifications/local-notif-parent/local-notif-data/retrieve-object.png" alt="retrieve object" class="no-border" >}} -3. Add a JavaScript Action Call activity to your nanoflow. +3. Add a **Call JavaScript action** activity to your nanoflow. 4. Double-click the action call activity. 5. Click **JavaScript Action** > **Select**. 6. Type *GetGuid* into the search field, click **GetGuid**, and click **Select**. (You are able to find the GetGuid JavaScript action because it is included in the NanoflowCommons module inside the Native Quickstarter template.) @@ -141,7 +142,7 @@ Next you will learn how to pass data to pages after you have tapped a notificati {{< figure src="/attachments/howto/mobile/native-mobile/implementation/notifications/local-notif-parent/local-notif-data/guid-nano-with-four-strings.png" alt="actionname" width="500" class="no-border" >}} -11. Drag a JavaScript action call activity into your nanoflow. +11. Drag a **Call JavaScript action** activity into your nanoflow. 12. Double-click the action call. 13. Click **JavaScript action** > **Select**. 14. Type *DisplayNotification* into the search field, click the corresponding JavaScript action, and click **Select**. @@ -164,8 +165,8 @@ Good job! When a user taps a notification from the **Pass GUID to Notification** {{< figure src="/attachments/howto/mobile/native-mobile/implementation/notifications/local-notif-parent/local-notif-data/notif-entity.png" alt="guid button" class="no-border" >}} -6. Drag a JavaScript action call into your nanoflow. -7. Double-click the JavaScript action call, then click **Select**. +6. Drag a **Call JavaScript action** activity into your nanoflow. +7. Double-click the Call JavaScript action activity, then click **Select**. 8. Type *GetObjectByGuid* into the search field, click that action, then click **Select**. 9. Click **TestEntity** and then click **Select**. 10. Next to the **Object guid** drop-down menu click **Edit**. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/_index.md index e752dcd994a..365c286b651 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/_index.md @@ -25,7 +25,7 @@ Most activities can be used in both microflows and nanoflows. However, some can | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/commit-object.png" alt="commit object" link="/refguide/committing-objects/" max-width=80% class="no-border" >}} | [Commit object(s)](/refguide/committing-objects/) | Allows you to commit changes to one or more objects. | | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/create-object.png" alt="create object" link="/refguide/create-object/" max-width=80% class="no-border" >}} | [Create object](/refguide/create-object/) | Creates an object. | | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/delete-object.png" alt="delete object" link="/refguide/deleting-objects/" max-width=80% class="no-border" >}} | [Delete object(s)](/refguide/deleting-objects/) | Deletes an object. | -| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/retrieve.png" alt="retrieve" link="/refguide/retrieve/" max-width=80% class="no-border" >}} | [Retrieve](/refguide/retrieve/) | Gets one (or more) associated objects of another object. Furthermore, this activity can also get one or more objects directly from a database. | +| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/retrieve.png" alt="retrieve" link="/refguide/retrieve-objects/" max-width=80% class="no-border" >}} | [Retrieve object(s)](/refguide/retrieve-objects/) | Gets one (or more) associated objects of another object. Furthermore, this activity can also get one or more objects directly from a database. | | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/rollback.png" alt="rollback object" link="/refguide/rollback-object/" max-width=80% class="no-border" >}} | [Rollback object](/refguide/rollback-object/) | Rolls uncommitted changes back that were made to an object in the part of the microflow preceding the activity. Furthermore, it deletes objects that have been created but have never been committed. | ## List Activities @@ -39,15 +39,15 @@ Most activities can be used in both microflows and nanoflows. However, some can | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/create-list.png" alt="create list" link="/refguide/create-list/" max-width=65% class="no-border" >}} | [Create list](/refguide/create-list/) | Creates a (empty) list variable. | | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-operation.png" alt="list operation" link="/refguide/list-operation/" max-width=65% class="no-border" >}} | [List operation](/refguide/list-operation/) | Combines or compares two lists with objects of the same entity. | -## Action Call Activities +## Call Activities -[Action call activities](/refguide/action-call-activities/) can be used to call another microflow or to call a Java action. +[Call activities](/refguide/call-activities/) can be used to call another microflow, or to call a Java or JavaScript action. | Graphic | Name | Description | | --- | --- | --- | -| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-java-action.png" alt="Java action call" link="/refguide/java-action-call/" max-width=65% class="no-border" >}} | [Call Java action](/refguide/java-action-call/) (microflows only) | Calls a Java action. Arguments can be passed to the action and the result can be stored in a variable. | -| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-javascript-action.png" alt="javascript action call" link="/refguide/javascript-action-call/" max-width=65% class="no-border" >}} | [Call JavaScript action](/refguide/javascript-action-call/) (nanoflows only) | Calls a JavaScript action. Arguments can be passed to the action and the result can be stored in a variable. | -| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-microflow.png" alt="microflow call" link="/refguide/microflow-call/" max-width=65% class="no-border" >}} | [Microflow call](/refguide/microflow-call/) | Calls a microflow. Arguments can be passed to the microflow and the result can be stored in a variable. | +| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-java-action.png" alt="Call Java action" link="/refguide/call-java-action/" max-width=65% class="no-border" >}} | [Call Java action](/refguide/call-java-action/) (microflows only) | Calls a Java action. Arguments can be passed to the action and the result can be stored in a variable. | +| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-javascript-action.png" alt="call javascript action" link="/refguide/call-javascript-action/" max-width=65% class="no-border" >}} | [Call JavaScript action](/refguide/call-javascript-action/) (nanoflows only) | Calls a JavaScript action. Arguments can be passed to the action and the result can be stored in a variable. | +| {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/call-microflow.png" alt="call microflow" link="/refguide/microflow-call/" max-width=65% class="no-border" >}} | [Call microflow](/refguide/microflow-call/) | Calls a microflow. Arguments can be passed to the microflow and the result can be stored in a variable. | ## Variable Activities diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/_index.md index e440fe146f8..faa300547f3 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/_index.md @@ -1,16 +1,18 @@ --- -title: "Action Call Activities" -url: /refguide/action-call-activities/ +title: "Call Activities" +url: /refguide/call-activities/ weight: 30 +aliases: + - /refguide/action-call-activities/ --- ## Introduction -The following are the action call activities you can use in your microflow or nanoflow: +The following are the Call activities you can use in your microflow or nanoflow: -* [Java action call](/refguide/java-action-call/) (microflows only) – calls a Java action -* [JavaScript action call](/refguide/javascript-action-call/) (nanoflows only) – calls a JavaScript action -* [Microflow call](/refguide/microflow-call/) – calls a microflow +* [Call Java action](/refguide/call-java-action/) (microflows only) – calls a Java action +* [Call JavaScript action](/refguide/call-javascript-action/) (nanoflows only) – calls a JavaScript action +* [Call microflow](/refguide/microflow-call/) – calls a microflow ## Read More diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call.md index 9e9ca18ce42..153583cc0e5 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call.md @@ -1,7 +1,9 @@ --- -title: "Java Action Call" -url: /refguide/java-action-call/ +title: "Call Java Action" +url: /refguide/call-java-action/ weight: 10 +aliases: + - /refguide/java-action-call/ #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. --- @@ -11,15 +13,15 @@ This activity can only be used in microflows. ## Introduction -The **Java action call** activity can be used to call a [Java action](/refguide/java-actions/). Arguments can be passed to the action and the result can be stored. +The **Call Java action** activity can be used to call a [Java action](/refguide/java-actions/). Arguments can be passed to the action and the result can be stored. ## Properties There are two sets of properties for this activity, those in the dialog box on the left, and those in the properties pane on the right: -{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call/java-action-call-properties.png" alt="Java Action Call Properties" max-width=80% class="no-border" >}} +{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/java-action-call/java-action-call-properties.png" alt="Call Java Action Properties" max-width=80% class="no-border" >}} -The **Java action call** properties pane consists of the following sections: +The **Call Java action** properties pane consists of the following sections: * [Action](#action) * [Common](#common) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/javascript-action-call.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/javascript-action-call.md index 22ededaafd3..d8747ff3a53 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/javascript-action-call.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/javascript-action-call.md @@ -1,8 +1,10 @@ --- -title: "JavaScript Action Call" -url: /refguide/javascript-action-call/ +title: "Call JavaScript Action" +url: /refguide/call-javascript-action/ weight: 20 -description: "This reference explains the properties of the JavaScript action call activity." +description: "This reference explains the properties of the Call JavaScript action activity." +aliases: + - /refguide/javascript-action-call/ #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. --- @@ -12,7 +14,7 @@ This activity can only be used in nanoflows. ## Introduction -The JavaScript action call activity can be used to call a [JavaScript action](/refguide/javascript-actions/). Arguments can be passed to the action, and the result can be stored. +The Call JavaScript action activity can be used to call a [JavaScript action](/refguide/javascript-actions/). Arguments can be passed to the action, and the result can be stored. ## Properties @@ -20,7 +22,7 @@ There are two sets of properties for this activity, those in the dialog box on t {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/javascript-action-call/javascript-action-call.png" alt="JavaScript Action Properties" width="700px" class="no-border" >}} -The **JavaScript action call** properties pane consists of the following sections: +The **Call JavaScript action** properties pane consists of the following sections: * [Action](#action) * [Common](#common) @@ -72,4 +74,4 @@ The name of the variable, list, or object returned by the activity. If it is an * [JavaScript Actions](/refguide/javascript-actions/) * [Build JavaScript Actions](/howto/extensibility/build-javascript-actions/) * [Nanoflows](/refguide/nanoflows/) -* [Java Action Call](/refguide/java-action-call/) +* [Call Java Action](/refguide/call-java-action/) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call.md index 9c49738e220..2a5c200b347 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call.md @@ -1,5 +1,5 @@ --- -title: "Microflow Call" +title: "Call Microflow" url: /refguide/microflow-call/ #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. --- @@ -10,15 +10,15 @@ This activity can be used in both microflows and nanoflows. ## Introduction -The **Microflow call** activity can be used to call a [microflow](/refguide/microflows/). Arguments can be passed to the microflow and the result can be stored. +The **Call microflow** activity can be used to call a [microflow](/refguide/microflows/). Arguments can be passed to the microflow and the result can be stored. ## Properties There are two sets of properties for this activity, those in the dialog box on the left, and those in the properties pane on the right: -{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call/microflow-call-properties.png" alt="Microflow Call Properties" width="700px" class="no-border" >}} +{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/action-call-activities/microflow-call/microflow-call-properties.png" alt="Call Microflow Properties" width="700px" class="no-border" >}} -The **Microflow call** properties pane consists of the following sections: +The **Call microflow** properties pane consists of the following sections: * [Action](#action) * [Common](#common) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/_index.md index 9bd93dd423a..2ecdb66e082 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/_index.md @@ -10,7 +10,7 @@ weight: 50 The following are the client activities you can use in your microflow or nanoflow: -* [Nanoflow call](/refguide/nanoflow-call/) (nanoflows only) – calls another nanoflow +* [Call nanoflow](/refguide/nanoflow-call/) (nanoflows only) – calls another nanoflow * [Close page](/refguide/close-page/) – closes the currently open page * [Download file](/refguide/download-file/) (microflows only) – downloads a file using the browser * [Show home page](/refguide/show-home-page/) (microflows only) – opens the home page for the end-user 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 3999f17fae9..252f1386f55 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 @@ -53,7 +53,7 @@ Double-click a row in the table or select it and click **Edit parameter value**, The **Output** section shows what the action returns and allows you to rename it. You can use this value in the microflow, or choose not to use it. -If the action returns an entity that has associations, you can select the associations that you want to have populated in the resulting variable. You can then use the **Retrieve** activity to retrieve the associated objects over the association. +If the action returns an entity that has associations, you can select the associations that you want to have populated in the resulting variable. You can then use the **Retrieve object(s)** activity to retrieve the associated objects over the association. ## Documentation Tab {#public-documentation} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/_index.md index b4bc4afaf7e..5cab0bc4e15 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/_index.md @@ -11,7 +11,7 @@ List activities work differently in microflows and in nanoflows. In nanoflows, c When working with the Mendix Platform, you can use microflows to manipulate not only single objects but whole lists of entities with a single activity. -Additional activities which work on lists, [commit object(s)](/refguide/committing-objects/), [delete object(s)](/refguide/deleting-objects/), and [retrieve](/refguide/retrieve/), are in the [Object Activities](/refguide/object-activities/) section of the toolbox. You can also [loop](/refguide/loop/) through a list to perform activities on the individual objects. +Additional activities which work on lists, [commit object(s)](/refguide/committing-objects/), [delete object(s)](/refguide/deleting-objects/), and [retrieve object(s)](/refguide/retrieve-objects/), are in the [Object Activities](/refguide/object-activities/) section of the toolbox. You can also [loop](/refguide/loop/) through a list to perform activities on the individual objects. The activities described in this document are in the **List Activities** section of the **Toolbox**. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/aggregate-list.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/aggregate-list.md index de2bc9724fc..0635b50422f 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/aggregate-list.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/aggregate-list.md @@ -103,11 +103,11 @@ The name of the variable in which the result of the aggregation is stored. The v ## Optimizing Aggregate Activities -In some apps, it is necessary to evaluate large datasets in a microflow (for example, for reporting purposes). If there are a lot of [retrieves](/refguide/retrieve/) and aggregates on large datasets in a microflow, it is easy to run into performance or memory problems. +In some apps, it is necessary to evaluate large datasets in a microflow (for example, for reporting purposes). If there are a lot of [retrieves](/refguide/retrieve-objects/) and aggregates on large datasets in a microflow, it is easy to run into performance or memory problems. This section describes how Mendix Runtime optimizes **Aggregate list** activities with large datasets and some recommended approaches for optimization. -When a database **Retrieve** activity is only used once in one **Aggregate list** activity, a custom range is not configured and the activity does not use an expression, the Mendix Runtime can automatically merge these two activities into a single action. This executes a single aggregate query on the database. So, if you retrieve all 100k log lines from a database and only do a count on the list, you will not receive a heap space. This is because the microflow never places all 100k records in memory. +When a database **Retrieve object(s)** activity is only used once in one **Aggregate list** activity, a custom range is not configured and the activity does not use an expression, the Mendix Runtime can automatically merge these two activities into a single action. This executes a single aggregate query on the database. So, if you retrieve all 100k log lines from a database and only do a count on the list, you will not receive a heap space. This is because the microflow never places all 100k records in memory. For instance, in this microflow, the Mendix Runtime merges the two activities into one single count query: @@ -135,4 +135,4 @@ Since the Mendix Runtime merges list retrieve and aggregate activities, you do n ## Read More -* [Retrieve Activities](/refguide/retrieve/) +* [Retrieve Activities](/refguide/retrieve-objects/) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow.md index 707ea194d21..a6345abba3b 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow.md @@ -67,7 +67,7 @@ Before you continue, you should first set up a test app, and populate it with te ## Retrieving and Filtering a List of Objects from the Database -Use a microflow with a [Retrieve](/refguide/retrieve/) activity to retrieve a list of objects, and then filter that list by applying an [XPath constraint](/refguide/xpath-constraints/). For example, the microflow can retrieve all orders from the database, and then filter that list to only the orders with the **Processing** status. +Use a microflow with a [Retrieve object(s)](/refguide/retrieve-objects/) activity to retrieve a list of objects, and then filter that list by applying an [XPath constraint](/refguide/xpath-constraints/). For example, the microflow can retrieve all orders from the database, and then filter that list to only the orders with the **Processing** status. 1. Create a new microflow by right-clicking your module and selecting **Add** > **Microflow**. 2. In the **Add Microflow** dialog box, in the **Name** field, enter *IVK_SetOrderToComplete*, and then click **OK**. @@ -81,12 +81,12 @@ Use a microflow with a [Retrieve](/refguide/retrieve/) activity to retrieve a li {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581054.png" alt="Selecting the caption and microflow" class="no-border" >}} 6. Open the **IVK_SetOrderToComplete** microflow by right-clicking the new button and selecting **Go to microflow**. -7. Open the **Toolbox** and search for the **Retrieve** activity. -8. Drag a **Retrieve** activity from the **Toolbox** to the line between the start and end events. +7. Open the **Toolbox** and search for the **Retrieve object(s)** activity. +8. Drag a **Retrieve object(s)** activity from the **Toolbox** to the line between the start and end events. - {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581091.png" alt="A view of the microflow with the Retrieve activity" class="no-border" >}} + {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581091.png" alt="A view of the microflow with the Retrieve object(s) activity" class="no-border" >}} -9. Double-click the **Retrieve** activity, and then set the following properties: +9. Double-click the **Retrieve object(s)** activity, and then set the following properties: * **Source** – select **From database** * **Entity** – select **Order** * **List** – enter *OrderList* @@ -103,7 +103,7 @@ After retrieving a list of orders with the status **Processing**, use a [loop](/ 1. Open the **IVK_SetOrderToComplete** microflow that you created in the previous section. 2. Drag a **Loop** activity from the **Toolbox**, and place it between the **OrderProcessingList** activity and the end event of the microflow. - {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581086.png" alt="Microflow with a Retrieve activity followed by a Loop activity" class="no-border" >}} + {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581086.png" alt="Microflow with a Retrieve object(s) activity followed by a Loop activity" class="no-border" >}} 3. Double-click the **Loop** activity. 4. In the **Iterate over** list, select **OrderList**, and then click **OK**. @@ -138,18 +138,18 @@ To calculate the total sum of all your orders via a loop, create a variable whic 1. On the **Orders** overview page, add a new **Call microflow** button with the following settings: * **Caption** – enter *Calculate Total Order Price* * **Name** – enter *IVK_CalculateTotalPriceOrders* -2. In the **IVK_CalculateTotalPriceOrders** microflow, add a **Retrieve** activity from the **Toolbox** to the line between the start and end events. -3. Double-click the **Retrieve** activity, and then set the following properties: +2. In the **IVK_CalculateTotalPriceOrders** microflow, add a **Retrieve object(s)** activity from the **Toolbox** to the line between the start and end events. +3. Double-click the **Retrieve object(s)** activity, and then set the following properties: * **Source** – select **From database** * **Entity** – select **Order** * **List** – enter *OrderList* -4. Drag a **Loop** activity from the **Toolbox**, and place it between the **Retrieve** activity and the end event of the microflow. +4. Drag a **Loop** activity from the **Toolbox**, and place it between the **Retrieve object(s)** activity and the end event of the microflow. 5. Double-click the **Loop** activity. 6. In the **Iterate over** list, select **OrderList**, and then click **OK**. {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581106.png" alt="Configuring the Loop activity to iterate over a list" class="no-border" >}} -7. Drag a **Create variable** activity from the **Toolbox** and place it before the **Retrieve** activity. +7. Drag a **Create variable** activity from the **Toolbox** and place it before the **Retrieve object(s)** activity. {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/list-activities/working-with-lists-in-a-microflow/18581073.png" alt="A microflow with a Create variable activity" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/ml-kit-activities/call-ml-model.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/ml-kit-activities/call-ml-model.md index 93e7e23f75b..80677895ea9 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/ml-kit-activities/call-ml-model.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/ml-kit-activities/call-ml-model.md @@ -23,7 +23,7 @@ To get started with machine learning models, check out [Using ML Kit](/refguide/ ### Action * **ML model mapping** – the [ML model mapping](/refguide/ml-model-mapping/) model -* **Input object** – the inputObject, defined in the microflow with a [Create Object](/refguide/create-object/) or [Java Action Call](/refguide/java-action-call/), and expects the same object type (not the entity) as in the **model mapping** +* **Input object** – the inputObject, defined in the microflow with a [Create Object](/refguide/create-object/) or [Call Java Action](/refguide/call-java-action/), and expects the same object type (not the entity) as in the **model mapping** ### Output diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/_index.md index aaeab2f64b1..486cc843b93 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/_index.md @@ -20,7 +20,7 @@ The following are the object activities you can use in your microflow or nanoflo * [Commit object(s)](/refguide/committing-objects/) – either stores objects of persistable entities in the database or stores objects of non-persistable entities in memory to allow them to be rolled back * [Create object](/refguide/create-object/) – creates an object * [Delete object(s)](/refguide/deleting-objects/) – activity deletes one or more objects -* [Retrieve](/refguide/retrieve/) – gets one or more objects of an entity +* [Retrieve object(s)](/refguide/retrieve-objects/) – gets one or more objects of an entity * [Rollback object](/refguide/rollback-object/) – undoes uncommitted changes made to an object {{% alert color="info" %}} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object.md index e224a0f9c93..ba2c52e33b4 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object.md @@ -18,7 +18,7 @@ For more information about specialization and generalization, see [Entities](/re An example of cast object properties is represented in the image below: -{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png" alt="cast object properties" width="650px" class="no-border" >}} +{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png" alt="cast object properties" width="650px" >}} There are two sets of properties for this activity, those in the dialog box on the left, and those in the properties pane on the right. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve.md index e51ce56f40a..a021df53077 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve.md @@ -1,7 +1,9 @@ --- -title: "Retrieve" -url: /refguide/retrieve/ +title: "Retrieve Object(s)" +url: /refguide/retrieve-objects/ weight: 60 +aliases: + - /refguide/retrieve/ #To update screenshots of these microflows in Studio Pro, use the Microflow Screenshots app. #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. --- @@ -12,17 +14,17 @@ This activity can be used in both microflows and nanoflows. ## Introduction -A **Retrieve** activity can be used to get one or more objects, either by directly traversing an association of another object, or by retrieving objects from the database. +A **Retrieve object(s)** activity can be used to get one or more objects, either by directly traversing an association of another object, or by retrieving objects from the database. ## Properties -An example of retrieve activity properties is represented in the image below: +An example of retrieve object(s) activity properties is represented in the image below: {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve/retrieve-properties.png" alt="retrieve properties" width="700px" class="no-border" >}} There are two sets of properties for this activity, those in the dialog box on the left, and those in the properties pane on the right. -The retrieve properties pane consists of the following sections: +The retrieve object(s) properties pane consists of the following sections: * [Action](#action) * [Common](#common) @@ -58,7 +60,7 @@ Any changes made to an object are visible in all widgets. This is because change #### Association -This property specifies which association is followed. The association must be an association from an object that is already available to the retrieve activity. Associations can be followed in both directions. +This property specifies which association is followed. The association must be an association from an object that is already available to the retrieve object(s) activity. Associations can be followed in both directions. ### Retrieve from Database Properties {#from-database} @@ -71,7 +73,7 @@ This property specifies the entity from which to retrieve instances (objects). The [XPath constraint](/refguide/xpath-constraints/) defines the condition the objects need to fulfill to be retrieved. If there is no XPath constraint, all objects of the entity are retrieved. {{% alert color="info" %}} -Date functions, user-role tokens, computations based on tokens, and following associations are not supported in XPath constraints when the retrieve activity is in a nanoflow. +Date functions, user-role tokens, computations based on tokens, and following associations are not supported in XPath constraints when the retrieve object(s) activity is in a nanoflow. {{% /alert %}} #### Range @@ -132,7 +134,7 @@ As we can see in the example below, the **GetCustomerPrimaryAddress** sub-microf Sometimes you only need to retrieve a specific instance of an object. Building a sub-microflow for just one retrieve-and-create action is too much work. An alternative way is to build your own loop, which allows you to have one main microflow but still be able to find and create objects during this process. -However, there is the risk of creating an infinite loop if the retrieve activity applies a constraint that is not set correctly during the create activity. So, always make sure to print a log message so that you can easily identify any problems in your design. +However, there is the risk of creating an infinite loop if the retrieve object(s) activity applies a constraint that is not set correctly during the create activity. So, always make sure to print a log message so that you can easily identify any problems in your design. {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/retrieve/retrieve-one-object-instance.png" width="400px" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object.md index 564ed50fa6c..a1ec44691a4 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object.md @@ -20,7 +20,7 @@ When the rollback object activity is performed in a sub-microflow, it rolls back An example of rollback object properties is represented in the image below: -{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png" alt="rollback object properties" width="650px" class="no-border" >}} +{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png" alt="rollback object properties" width="650px" >}} There are two sets of properties for this activity, those in the dialog box on the left, and those in the properties pane on the right. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/workflow-activities/workflow-call.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/workflow-activities/workflow-call.md index 33ed2aecd73..1a8adcb5a70 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/workflow-activities/workflow-call.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/workflow-activities/workflow-call.md @@ -48,7 +48,7 @@ The object which you want to use as a context. It should be of the entity type s ### Use Return Value -This property determines if the returned value from the called workflow should be available in the rest of the current microflow. If **Use return value** is set to **Yes**, you will need to fill in the [variable name](/refguide/microflow-call/#name) of the workflow object returned by the activity. +This property determines if the returned value from the called workflow should be available in the rest of the current microflow. If **Use return value** is set to **Yes**, you will need to fill in the [variable name](/refguide/call-microflow/#name) of the workflow object returned by the activity. ### Variable Name {#name} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/annotation.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/annotation.md index 3126cd4657b..723a00f39d4 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/annotation.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/annotation.md @@ -26,6 +26,6 @@ For details, see [Common Properties](/refguide/microflow-element-common-properti An annotation flow is a connection that can be used to link an annotation to a flow object (or objects). -For example, this is an annotation flow linking an annotation and a **Microflow call** activity: +For example, this is an annotation flow linking an annotation and a **Call microflow** activity: {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/annotation/anotation-flow.png" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events/end-event.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events/end-event.md index 31ca5330047..23917372a40 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events/end-event.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events/end-event.md @@ -56,5 +56,5 @@ When you update the return type, a default variable name is set based on the ret ## Read More * [Start Event](/refguide/start-event/) -* [Microflow Call](/refguide/microflow-call/) +* [Call Microflow](/refguide/microflow-call/) * [Call Nanoflow](/refguide/nanoflow-call/) diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-handling-in-microflows.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-handling-in-microflows.md index ec9f9be2cdb..843d1339a25 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-handling-in-microflows.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-handling-in-microflows.md @@ -88,7 +88,7 @@ When **Microflow 1** starts with a button click, a savepoint is created at the v ### Error Handling - Continue -The **Continue** option can only be set on a microflow call or on a loop. +The **Continue** option can only be set on a Call microflow activity or on a loop. In this example, the error handling in **Microflow 2** is set to **Continue**. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/microflow.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/microflow.md index fdefbd39335..bfc9b313dd1 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/microflow.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/microflow.md @@ -89,7 +89,7 @@ Default: *disabled* #### Apply Entity Access -**Apply entity access** indicates whether entity access based on the current user is applied when performing operations on objects. Enabling this setting limits the objects that are retrieved by the [retrieve activity](/refguide/retrieve/) to only those that the current user is allowed to see. Similarly, when reading and writing attributes and associations, the entity access of the current user is applied. Conversely, if entity access is not applied, all operations are allowed and all objects are retrieved. +**Apply entity access** indicates whether entity access based on the current user is applied when performing operations on objects. Enabling this setting limits the objects that are retrieved by the [retrieve object(s) activity](/refguide/retrieve-objects/) to only those that the current user is allowed to see. Similarly, when reading and writing attributes and associations, the entity access of the current user is applied. Conversely, if entity access is not applied, all operations are allowed and all objects are retrieved. | Option | Description | | --- | --- | diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/retrieving-current-user-with-a-microflow.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/retrieving-current-user-with-a-microflow.md index f8db1977801..4284243070a 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/retrieving-current-user-with-a-microflow.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/retrieving-current-user-with-a-microflow.md @@ -31,9 +31,9 @@ Before you continue, make sure you have completed the following: To retrieve the currently logged-in user using the **Account** entity from the **Administration** module, do the following: 1. Open an existing microflow or create a new one. -2. Navigate to the **Toolbox** and search for the **Retrieve** activity. -3. Drag the **Retrieve** activity into your microflow. -4. Double-click the **Retrieve** activity to open its properties. +2. Navigate to the **Toolbox** and search for the **Retrieve object(s)** activity. +3. Drag the **Retrieve object(s)** activity into your microflow. +4. Double-click the **Retrieve object(s)** activity to open its properties. 5. Choose **From database** as the **Source**. 6. Click **Select...** for **Entity**. 7. In the **Select Entity** dialog box, go to **Marketplace modules** > **Administration**, and select **Account**. diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing-microflows-with-unit-testing.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing-microflows-with-unit-testing.md index e03d5b2c82b..ad39cc7e166 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing-microflows-with-unit-testing.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing-microflows-with-unit-testing.md @@ -122,12 +122,12 @@ To create a sample test microflow, follow these steps: 8. In the **Member** section of the activity, add another new member with the following properties: * **Level** – *MyFirstModule.Level.Junior* * **Member type** – **Enumeration 'Level'** -9. In the **Test_PromoteEmployeeToMedior** microflow, call the **Promote** microflow by adding a **Microflow Call** activity with the following properties: +9. In the **Test_PromoteEmployeeToMedior** microflow, call the **Promote** microflow by adding a **Call Microflow** activity with the following properties: * **Microflow** – **MyFirstModule.Promote** * **Parameter** – **Employee** * **Argument** –*$NewEmployee* - {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing/call-promote-microflow.png" alt="A microflow call activity with Employee as the parameter" max-width=70% >}} + {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/testing/call-promote-microflow.png" alt="A call microflow activity with Employee as the parameter" max-width=70% >}} 10. To test if the employee is promoted to the right level, add an **Assert using expression** activity with the following properties: * **Name** – *‘Promoted to Medior?’* diff --git a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/_index.md b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/_index.md index 048244011d0..27fbd52b14d 100644 --- a/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/nanoflows/_index.md @@ -28,7 +28,7 @@ The following activities interact with the database: * [Create object](/refguide/create-object/) * [Commit object(s)](/refguide/committing-objects/) -* [Retrieve](/refguide/retrieve/) +* [Retrieve object(s)](/refguide/retrieve-objects/) * [Rollback object](/refguide/rollback-object/) Therefore, the best practice is to use nanoflows in online applications when they do not contain the above activities. diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox.md b/content/en/docs/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox.md index c2e1b4a31be..331135bd478 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox.md @@ -44,11 +44,11 @@ To create the calling microflow and add it as the custom action to the workflow 1. Create a new microflow that calls **ACT_SAP_INVENTORY_LAPTOP_CHECK**. Name the new microflow **WFS_MY_SYSTEM_TASK**. 2. Make sure that the input parameters of the **WFS_MY_SYSTEM_TASK** microflow are mapped to the workflow definition. For the **Employee_Onboarding** workflow, add the EmployeeOnboarding parameter because the **EmployeeOnboarding** entity is set as the **Workflow entity**. -3. In **Toolbox**, select **Microflow call** and drag it to the flow: +3. In **Toolbox**, select **Call microflow** and drag it to the flow: - {{< figure src="/attachments/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox/microflow-call.png" alt="Microflow call action" class="no-border" >}} + {{< figure src="/attachments/refguide/modeling/application-logic/workflows/add-action-to-workflow-toolbox/microflow-call.png" alt="Call microflow activity" class="no-border" >}} -4. Double-click the **Microflow call** activity to open its properties and set **Microflow** to **ACT_SAP_INVENTORY_LAPTOP_CHECK**. +4. Double-click the **Call microflow** activity to open its properties and set **Microflow** to **ACT_SAP_INVENTORY_LAPTOP_CHECK**. 5. Click the **End event** and navigate to the **Properties** pane. 6. Set the **Return value** for it to **Boolean**. 7. Right-click the working area of the microflow and select **Properties**. diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md index a1d9f733624..91e740ec647 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md @@ -27,7 +27,7 @@ The elements of this category are described in the table below: | Graphic | Element | Description | | ----------------------------------------------------------- | --------------------------------- | ------------------------------------------------------------ | -| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/start-event.png" alt="Start Event" class="no-border" >}} | Start event | The starting point of a workflow. Workflows are triggered either by the [Call workflow](/refguide/on-click-event/#call-workflow) on-click event on pages or by the [Call workflow](/refguide/workflow-call/) action in microflows.
Click the start event to open [workflow properties](/refguide/workflow-properties/). | +| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/start-event.png" alt="Start Event" class="no-border" >}} | Start event | The starting point of a workflow. Workflows are triggered either by the [Call workflow](/refguide/on-click-event/#call-workflow) on-click event on pages or by the [Call workflow](/refguide/workflow-call/) activity in microflows.
Click the start event to open [workflow properties](/refguide/workflow-properties/). | | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/annotation.png" alt="Annotation" class="no-border" >}} | Annotation | An annotation is an element that can be used to put comments to a flow. For example, you can add a comment for your team that one of the user tasks needs to be changed later.
You can add annotations to the workflow or to individual activities. To add the annotation to the workflow, drag and drop the annotation in the editor's working area. To add the annotation to the activity, drag and drop it inside the activity. | | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/decision.png" alt="Decision" class="no-border" >}} | [Decision](/refguide/decision-in-workflows/) | Makes a choice based on a condition and follows one and only one of the outgoing paths. | | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/parallel-split.png" alt="Parallel Split" class="no-border" >}} | [Parallel split](/refguide/parallel-split/) | Adds two parallel paths to your workflow. | diff --git a/content/en/docs/refguide/modeling/domain-model/associations/query-over.md b/content/en/docs/refguide/modeling/domain-model/associations/query-over.md index bc820df495b..c126f319129 100644 --- a/content/en/docs/refguide/modeling/domain-model/associations/query-over.md +++ b/content/en/docs/refguide/modeling/domain-model/associations/query-over.md @@ -98,7 +98,7 @@ If the $ChosenFolder object is `SubFolder2`, you will retrieve all the **File** ## Associations to Specializations -In the special case of self-reference when a one-to-many association is with a specialization of itself, you cannot retrieve [by association](/refguide/retrieve/#source). +In the special case of self-reference when a one-to-many association is with a specialization of itself, you cannot retrieve [by association](/refguide/retrieve-objects/#source). Here is an example inheritance: diff --git a/content/en/docs/refguide/modeling/domain-model/entities/persistability.md b/content/en/docs/refguide/modeling/domain-model/entities/persistability.md index 10e264b4445..d2e2d7162bd 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/persistability.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/persistability.md @@ -26,7 +26,7 @@ However, performing a rollback on persistable autocommitted objects or objects w ## Non-Persistable Entities {#non-persistable} -Non-persistable entities are stored in the runtime memory and never get committed to the database. Therefore, they have no table in the database and the only way to retrieve them is [over associations](/refguide/retrieve/#association). +Non-persistable entities are stored in the runtime memory and never get committed to the database. Therefore, they have no table in the database and the only way to retrieve them is [over associations](/refguide/retrieve-objects/#association). Committing non-persistable entities records the current attribute values and association values in memory, allowing a rollback to revert to these values. diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md index 32fca04e97b..e9c8ae2aaef 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md @@ -99,7 +99,7 @@ An OQL query can begin with either a `SELECT` clause or a `FROM` clause, as both #### `ORDER BY` Is Only Needed with `LIMIT` or `OFFSET` -Similar to other types of Mendix entity, view entities represent data without enforcing any specific order. Therefore, using the `ORDER BY` clause in the view entity query to sort query results is neither possible nor necessary. Data retrieved from a view entity can be sorted on retrieval (like regular entities) using options like the [Sorting](/refguide/retrieve/#sorting) feature in a Retrieve microflow activity. +Similar to other types of Mendix entity, view entities represent data without enforcing any specific order. Therefore, using the `ORDER BY` clause in the view entity query to sort query results is neither possible nor necessary. Data retrieved from a view entity can be sorted on retrieval (like regular entities) using options like the [Sorting](/refguide/retrieve-objects/#sorting) feature in a Retrieve microflow activity. The `ORDER BY` clause is only required in a view entity when using `LIMIT` or `OFFSET` to create data subsets. For example, you might need to use `ORDER BY` when retrieving: diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md index 82726972783..b5d64cd32d2 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md @@ -70,7 +70,7 @@ The original customer view included address information, but most database optim ## Sorting of View Entity Results {#sorting} -Similar to other types of Mendix entity, view entities represent data without enforcing any specific order. As a result, it is not possible to use the `ORDER BY` clause in the view entity OQL to sort query results. However, data retrieved from a view entity can be sorted on retrieval (like regular entities) using options like the [Sorting](/refguide/retrieve/#sorting) feature in a Retrieve microflow activity. +Similar to other types of Mendix entity, view entities represent data without enforcing any specific order. As a result, it is not possible to use the `ORDER BY` clause in the view entity OQL to sort query results. However, data retrieved from a view entity can be sorted on retrieval (like regular entities) using options like the [Sorting](/refguide/retrieve-objects/#sorting) feature in a Retrieve microflow activity. ### `ORDER BY` in Combination with `LIMIT` and `OFFSET` diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/view-entity-overview-pages.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/view-entity-overview-pages.md index 48ac129eda5..6116f6a4f1a 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/view-entity-overview-pages.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/view-entity-overview-pages.md @@ -137,7 +137,7 @@ On the Product overview page above, there is no button to add or modify a produc 1. Create a microflow and name it *ACT_UpdateProduct*. 2. Add a parameter and in the entity field and select **ProductOverviewVE**. -3. Add a [retrieve](/refguide/retrieve/) activity. In this activity, retrieve a *Product* object from the database. Configure the activity with the following details: +3. Add a [retrieve object(s)](/refguide/retrieve-objects/) activity. In this activity, retrieve a *Product* object from the database. Configure the activity with the following details: * Use the following XPath constraint: @@ -222,7 +222,7 @@ The final data view should look like this: Once the Product page is complete, update the related microflow. To do this, follow the steps below: 1. Open the **ACT_UpdateProduct** microflow. -2. Add a Retrieve activity after the existing Retrieve product activity. +2. Add a Retrieve object(s) activity after the existing Retrieve product activity. 3. Retrieve a Category object from the database. Configure the activity using the following details: * Use the following XPath constraint: @@ -233,7 +233,7 @@ Once the Product page is complete, update the related microflow. To do this, fol * In the Range field, select **First** -4. Add another Retrieve activity to retrieve the Supplier object. Configure the activity using the following details: +4. Add another Retrieve object(s) activity to retrieve the Supplier object. Configure the activity using the following details: * Use the following XPath constraint: diff --git a/content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/export-xml-documents.md b/content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/export-xml-documents.md index 7d827c563f1..a3aa3951a71 100644 --- a/content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/export-xml-documents.md +++ b/content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/export-xml-documents.md @@ -123,7 +123,7 @@ To create the export logic, follow these steps: 5. Select the input parameter and delete it. 6. Open the **Toolbox**, which should be on the lower-right side of Studio Pro (you can also open it from the **View** menu). -7. Drag a **Retrieve** activity from the **Toolbox** to the line between the start event and end event. +7. Drag a **Retrieve object(s)** activity from the **Toolbox** to the line between the start event and end event. 8. Double-click the activity to open the **Retrieve Objects** properties editor and do the following: * For **Source**, select **From database** * For **Entity**, click **Select...** and select the customer entity diff --git a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/_index.md b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/_index.md index eb1ae867ad8..abeb8f016f6 100644 --- a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/_index.md +++ b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/_index.md @@ -200,7 +200,7 @@ xmlHttp.send(null); Specify which microflow to use for custom authentication. The microflow may take the following as a parameter: * A list of [HttpHeader](/refguide/http-request-and-response-entities/#http-header). These are the HTTP headers in the client's request. Use this parameter for authentication schemes that are based on HTTP headers. -* [HttpRequest](/refguide/http-request-and-response-entities/#http-request). Use this parameter for authentication schemes that are based on more than just the HTTP headers (for example, when the client supplies credentials in the request body). You cannot use this parameter together with a list of HttpHeader. Instead, use a [retrieve activity](/refguide/retrieve/) to retrieve the associated request headers. +* [HttpRequest](/refguide/http-request-and-response-entities/#http-request). Use this parameter for authentication schemes that are based on more than just the HTTP headers (for example, when the client supplies credentials in the request body). You cannot use this parameter together with a list of HttpHeader. Instead, use a [retrieve object(s) activity](/refguide/retrieve-objects/) to retrieve the associated request headers. * [HttpResponse](/refguide/http-request-and-response-entities/#http-response). When the microflow sets the status code of this response to something other then **200**, this value is returned and the operation will not be executed. Any headers set on the response are returned (except when the microflow returns an empty user). The authentication microflow should return a User. diff --git a/content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging.md b/content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging.md index ab9f19d71f2..bf215cd0564 100644 --- a/content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging.md +++ b/content/en/docs/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging.md @@ -10,7 +10,7 @@ aliases: ## Introduction -Using server-side paging and sorting for a microflow data source, you can model out how you retrieve data to a single page and ensure it ends up in the correct sorting order. With this approach, you do not need to return all the data to the client — you can just return a single page. This can be helpful for getting data from external sources like a REST service, but can also be useful for a regular retrieve activity in a microflow. To do this, you must model the logic for getting the correct data in the microflow itself. +Using server-side paging and sorting for a microflow data source, you can model out how you retrieve data to a single page and ensure it ends up in the correct sorting order. With this approach, you do not need to return all the data to the client — you can just return a single page. This can be helpful for getting data from external sources like a REST service, but can also be useful for a regular retrieve object(s) activity in a microflow. To do this, you must model the logic for getting the correct data in the microflow itself. This how-to teaches you how to do the following: @@ -67,11 +67,11 @@ Now, you can start calling the REST service from your microflow data source. To {{< figure src="/attachments/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging/call-rest-response.png" alt="variable result" width="500" class="no-border" >}} -10. From the **Toolbox**, drag the **Retrieve** activity into the microflow and double-click it. +10. From the **Toolbox**, drag the **Retrieve object(s)** activity into the microflow and double-click it. 11. Click **Association** > **Select**. 12. Click **Expand All** and select **JsonObject_Summary (List of NativeMobile.JsonObject)**. 13. Click **OK** to accept this association. -14. Right-click the **Retrieve** activity and select **Set $JsonObjectList as return value**: +14. Right-click the **Retrieve object(s)** activity and select **Set $JsonObjectList as return value**: {{< figure src="/attachments/refguide/modeling/integration/rest-services/consumed-rest-services/server-side-paging/call-rest-returned.png" alt="set return value" width="500" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-service/publish-rest-service.md b/content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-service/publish-rest-service.md index ae679eb070b..234e9977cd1 100644 --- a/content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-service/publish-rest-service.md +++ b/content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-service/publish-rest-service.md @@ -80,7 +80,7 @@ To create the mapping, follow these steps: {{< figure src="/attachments/refguide/modeling/integration/rest-services/publish-rest-service/ConvertOrderID.png" alt="Create Variable dialog box used to parse OrderID as an integer variable" class="no-border" >}} -10. Add a **Retrieve** activity to the microflow to retrieve the **Order** based on the **OrderID**. Set this activity to retrieve the first matching order from the database. +10. Add a **Retrieve object(s)** activity to the microflow to retrieve the **Order** based on the **OrderID**. Set this activity to retrieve the first matching order from the database. {{< figure src="/attachments/refguide/modeling/integration/rest-services/publish-rest-service/RetrieveOrder.png" alt="Range and XPath constraint settings in the Retrieve dialog box" >}} diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/best-practice-recommender/performance-best-practices.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/best-practice-recommender/performance-best-practices.md index add5a7c226d..104687a7171 100644 --- a/content/en/docs/refguide/modeling/mendix-ai-assistance/best-practice-recommender/performance-best-practices.md +++ b/content/en/docs/refguide/modeling/mendix-ai-assistance/best-practice-recommender/performance-best-practices.md @@ -18,7 +18,7 @@ This section outlines performance issues and Mendix best practices for optimizin When an object has calculated attributes, each time this object is changed or retrieved from the storage, its calculated attributes are computed by calling a microflow. If the logic behind calculated attributes retrieves other objects or executes Integration activities, it will result in an extra load (and delay) while the outcome of the logic is not used. Creating calculated attributes always affects performance, so you should evaluate whether it is necessary to use them. For more information on attributes, see [Attributes](/refguide/attributes/). -In most cases, the logic behind a calculated attribute is always executed when the object is used. It is executed whenever there is no retrieval schema for a Retrieve activity (which is the case with data grids). The logic behind calculated attributes is executed in the following elements: +In most cases, the logic behind a calculated attribute is always executed when the object is used. It is executed whenever there is no retrieval schema for a Retrieve object(s) activity (which is the case with data grids). The logic behind calculated attributes is executed in the following elements: * Retrieve and change object activities in microflows * In UI widgets (for example, data views, custom widgets) diff --git a/content/en/docs/refguide/modeling/menus/view-menu/errors-pane/clear-warning-messages.md b/content/en/docs/refguide/modeling/menus/view-menu/errors-pane/clear-warning-messages.md index cc597d01489..778640bdf83 100644 --- a/content/en/docs/refguide/modeling/menus/view-menu/errors-pane/clear-warning-messages.md +++ b/content/en/docs/refguide/modeling/menus/view-menu/errors-pane/clear-warning-messages.md @@ -163,7 +163,7 @@ Variable ‘Variable’ is never used. {{% /alert %}} * There are multiple potential causes here -* The solution involves removing the variable from the microflow, which could mean deleting the retrieve activity or electing to not use the return value of a microflow call +* The solution involves removing the variable from the microflow, which could mean deleting the retrieve object(s) activity or electing to not use the return value of a microflow call ## Read More diff --git a/content/en/docs/refguide/modeling/resources/java-actions.md b/content/en/docs/refguide/modeling/resources/java-actions.md index 09f244a6a20..14a2288d60d 100644 --- a/content/en/docs/refguide/modeling/resources/java-actions.md +++ b/content/en/docs/refguide/modeling/resources/java-actions.md @@ -8,7 +8,7 @@ description: "Describes using Java Actions to extend the functionality of your M ## Introduction -With Java actions you can extend the functionality of your application in situations where it would be hard to implement this functionality in microflows. You can call a Java action from a microflow using the [Java action call](/refguide/java-action-call/). +With Java actions you can extend the functionality of your application in situations where it would be hard to implement this functionality in microflows. You can call a Java action from a microflow using the [Call Java action](/refguide/call-java-action/). {{% alert color="info" %}} Each Java action defined in Studio Pro corresponds to a file *{name of Java action}.java* in the subdirectory *javasource/{module name}/actions* of the app directory. @@ -28,7 +28,7 @@ A Java action has zero or more parameters. Parameters are the means by which you Each parameter has a name, type, category, and description. -Use categories to keep the parameters apart in the [Java action call](/refguide/java-action-call/). If you do not specify a category, the parameter will appear in the **Input** group. +Use categories to keep the parameters apart in the [Call Java action](/refguide/call-java-action/). If you do not specify a category, the parameter will appear in the **Input** group. See [Data Types](/refguide/data-types/) for the possible standard parameter types. When the type is an Object or List, you must also select its Entity type, which can be either a specific entity or a type parameter. The type parameter postpones the selection of the actual entity type until the Java action is used in a microflow. This allows your Java action to accept a (list of) Mendix object (or objects) of an arbitrary entity type. diff --git a/content/en/docs/refguide/modeling/resources/javascript-actions.md b/content/en/docs/refguide/modeling/resources/javascript-actions.md index 4006125066f..1e5ee8fe7c4 100644 --- a/content/en/docs/refguide/modeling/resources/javascript-actions.md +++ b/content/en/docs/refguide/modeling/resources/javascript-actions.md @@ -12,7 +12,7 @@ This activity can only be used in **Nanoflows**. ## Introduction -With JavaScript actions, you can extend your application's functionality in ways nanoflows alone cannot. To use a JavaScript action, call it from a nanoflow using the [JavaScript Action Call](/refguide/javascript-action-call/). +With JavaScript actions, you can extend your application's functionality in ways nanoflows alone cannot. To use a JavaScript action, call it from a nanoflow using the [Call JavaScript Action](/refguide/call-javascript-action/) activity. {{% alert color="info" %}} @@ -74,7 +74,7 @@ This setting handles the parameter's name. A name is required. Names must start #### Category -Use categories to keep parameters apart in a [JavaScript Action Call](/refguide/javascript-action-call/). Categories are useful for making logical groups of parameters when your app has several parameters. If you do not specify a category, the parameter will appear in the **Input** group. +Use categories to keep parameters apart in a [Call JavaScript Action](/refguide/call-javascript-action/). Categories are useful for making logical groups of parameters when your app has several parameters. If you do not specify a category, the parameter will appear in the **Input** group. #### Description @@ -201,8 +201,8 @@ export async function Hello(message) { ## Read More -* [JavaScript Action Call](/refguide/javascript-action-call/) +* [Call JavaScript Action](/refguide/call-javascript-action/) * [Nanoflows](/refguide/nanoflows/) * [Build JavaScript Actions](/howto/extensibility/build-javascript-actions/) -* [Java Action Call](/refguide/java-action-call/) -* [Microflow Call](/refguide/microflow-call/) +* [Call Java Action](/refguide/call-java-action/) +* [Call Microflow](/refguide/microflow-call/) diff --git a/content/en/docs/refguide/modeling/resources/task-queue.md b/content/en/docs/refguide/modeling/resources/task-queue.md index e1aba38c98c..e802198d648 100644 --- a/content/en/docs/refguide/modeling/resources/task-queue.md +++ b/content/en/docs/refguide/modeling/resources/task-queue.md @@ -93,7 +93,7 @@ The method `executeInBackground` takes two parameters: a context and a queue nam #### In Studio Pro -In Studio Pro, a [Call Java action](/refguide/microflow-call/) activity can start a Java action in a Task Queue. +In Studio Pro, a [Call Java action](/refguide/call-java-action/) activity can start a Java action in a Task Queue. 1. Edit the **Call Java Action** activity. 2. Check the box **Execute this Java action in a Task Queue**. diff --git a/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md b/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md index 535196e2cfa..22024022afc 100644 --- a/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md +++ b/content/en/docs/refguide/modeling/xpath/xpath-constraints/_index.md @@ -22,7 +22,7 @@ All the Studio Pro examples below assume that an entity `Sales.Customer` is sele Visual Builder for XPath constraints has a number of limitations which are listed in [Builder Limitations](#limitations). {{% /alert %}} -You can use the Builder in all places where you can retrieve data from the database, for example a [Retrieve](/refguide/retrieve/) activity in a microflow or the [Data Source](/refguide/database-source/) of a widget. Select **(From) Database** and click **Edit…** next to **XPath constraint** to open a dialog box where you can build your constraint. +You can use the Builder in all places where you can retrieve data from the database, for example a [Retrieve object(s)](/refguide/retrieve-objects/) activity in a microflow or the [Data Source](/refguide/database-source/) of a widget. Select **(From) Database** and click **Edit…** next to **XPath constraint** to open a dialog box where you can build your constraint. You can switch between the Builder and the XPath expression editor to view them in different ways. You can also set the Builder as the default in your [preferences](/refguide/preferences-dialog/#visual-builder). @@ -81,7 +81,7 @@ If you try to use an unsupported feature you will be warned and can choose to ed In all versions of Mendix you can write XPath constraints using the syntax explained below. As you enter your XPath you will be given assistance to help you choose the correct entities, attributes, variables, and associations. You will also see if there are any syntax errors. -For all places where you can retrieve data from the database, for example a [Retrieve](/refguide/retrieve/) activity in a microflow or the [Data Source](/refguide/database-source/) of a widget, you select **(From) Database** and you will always have the option to add an **XPath constraint** by clicking **Edit…** to open a dialog box where you can enter your constraint. +For all places where you can retrieve data from the database, for example a [Retrieve object(s)](/refguide/retrieve-objects/) activity in a microflow or the [Data Source](/refguide/database-source/) of a widget, you select **(From) Database** and you will always have the option to add an **XPath constraint** by clicking **Edit…** to open a dialog box where you can enter your constraint. {{< figure src="/attachments/refguide/modeling/xpath/xpath-constraints/from-database-xpath-10-5.png" class="no-border" >}} diff --git a/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-operators.md b/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-operators.md index cb6ce710558..8e5952ad6bc 100644 --- a/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-operators.md +++ b/content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-operators.md @@ -20,7 +20,7 @@ The following operators can be used in XPath query constraints, both in Mendix S ## Mathematical operators -In Studio Pro, mathematical operators can be used in XPath constraints that are defined in the model such as the [Retrieve](/refguide/retrieve/) microflow activity or access rule [constraints](/refguide/access-rules/#xpath-constraints). +In Studio Pro, mathematical operators can be used in XPath constraints that are defined in the model such as the [Retrieve object(s)](/refguide/retrieve-objects/) microflow activity or access rule [constraints](/refguide/access-rules/#xpath-constraints). Mathematical operators are not allowed in queries that come from the client. For example, they cannot be used in [widgets](/appstore/widgets/). diff --git a/content/en/docs/refguide/runtime/runtime-java/runtime-java-errors.md b/content/en/docs/refguide/runtime/runtime-java/runtime-java-errors.md index f78b7cac57e..f1839b88d36 100644 --- a/content/en/docs/refguide/runtime/runtime-java/runtime-java-errors.md +++ b/content/en/docs/refguide/runtime/runtime-java/runtime-java-errors.md @@ -14,7 +14,7 @@ Some of the more common errors you can find in the application log that can caus ### java.lang.StackOverflowError -Your application is not going to recover from one of these errors. When you encounter one of these while running your Mendix application it is practically always going to be caused by an infinite loop. You can easily recreate this by creating a microflow called *Microflow* with a single microflow call action and selecting the microflow called *Microflow*. The infinite loop will crash your app and produce a stack overflow error. +Your application is not going to recover from one of these errors. When you encounter one of these while running your Mendix application it is practically always going to be caused by an infinite loop. You can easily recreate this by creating a microflow called *Microflow* with a single call microflow activity and selecting the microflow called *Microflow*. The infinite loop will crash your app and produce a stack overflow error. ### java.lang.OutOfMemoryError: Java heap space diff --git a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/show-page/show-page-properties.png b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/show-page/show-page-properties.png index f9bb0f83d11..066d8f0cdf2 100644 Binary files a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/show-page/show-page-properties.png and b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/show-page/show-page-properties.png differ diff --git a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png index 8154c45e794..52bd4836524 100644 Binary files a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png and b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/cast-object/cast-properties.png differ diff --git a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png index 7ad7a635033..1a86d7f4751 100644 Binary files a/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png and b/static/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/object-activities/rollback-object/rollback-properties.png differ