From 0ca4c820ac7d91801a311e577730d6441c6ebcd4 Mon Sep 17 00:00:00 2001 From: emirmx <53853302+emirmx@users.noreply.github.com> Date: Thu, 26 Jun 2025 10:26:40 +0200 Subject: [PATCH 1/3] Update query-over.md --- .../modeling/domain-model/associations/query-over.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) 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 6298a3c9287..6d51228aa1d 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 @@ -104,9 +104,8 @@ Here is an example inheritance: {{< figure src="/attachments/refguide/modeling/domain-model/associations/query-over/limitation.png" class="no-border" >}} -In this example, a list of **Specializations** cannot be retrieved when using a standard by-association retrieve in a microflow if the input is the specialization. - -However, there is a workaround for this limitation: The list of Specializations can be retrieved with a Java action using the Java API. This Java action needs two parameters: the **Specialization** and a Boolean **Reverse** via this code snippet: +In this example, if a standard by-association retrieve in a microflow is used starting from a `Specialization` this will return the `Specialization` that the starting point `Specialization` points to. +The list of `Generalization`'s that points to `Specialization` can be retrieved with a Java action using the Java API: ```java public class RetrieveAsAssociatedWithB extends CustomJavaAction> From b27f20db5da62870e3295511730d1774b481054c Mon Sep 17 00:00:00 2001 From: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com> Date: Thu, 3 Jul 2025 12:09:35 +0200 Subject: [PATCH 2/3] Clarify what user might expect but not get. Discussed in PR --- .../refguide/modeling/domain-model/associations/query-over.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 6d51228aa1d..847733598a4 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 @@ -104,7 +104,7 @@ Here is an example inheritance: {{< figure src="/attachments/refguide/modeling/domain-model/associations/query-over/limitation.png" class="no-border" >}} -In this example, if a standard by-association retrieve in a microflow is used starting from a `Specialization` this will return the `Specialization` that the starting point `Specialization` points to. +In this example, if a standard by-association retrieve in a microflow is used starting from a `Specialization` this will return the `Specialization` that the starting point `Specialization` points to and not the list of `Generalization` which are associated via the `Generalization_Specialization` association. The list of `Generalization`'s that points to `Specialization` can be retrieved with a Java action using the Java API: ```java From c5118209a4f08dada29ce04ad386df08f7f92704 Mon Sep 17 00:00:00 2001 From: Mark van Ments Date: Thu, 3 Jul 2025 12:25:49 +0200 Subject: [PATCH 3/3] Reinstate description of what Java Action does. --- .../refguide/modeling/domain-model/associations/query-over.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 847733598a4..bc820df495b 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 @@ -105,7 +105,8 @@ Here is an example inheritance: {{< figure src="/attachments/refguide/modeling/domain-model/associations/query-over/limitation.png" class="no-border" >}} In this example, if a standard by-association retrieve in a microflow is used starting from a `Specialization` this will return the `Specialization` that the starting point `Specialization` points to and not the list of `Generalization` which are associated via the `Generalization_Specialization` association. -The list of `Generalization`'s that points to `Specialization` can be retrieved with a Java action using the Java API: + +The list of `Generalization`'s that points to `Specialization` can be retrieved with a Java action using the [Runtime API](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/Core.html#retrieveByPath(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.lang.String,boolean)), as shown in this Java action which takes the `Specialization` object and a Boolean `Reverse` to indicate that the object instance is the child of the path of a self association: ```java public class RetrieveAsAssociatedWithB extends CustomJavaAction>