[55335] Fixes maximum calculation example in tutorial

Change-Id: I431c6b3ca96ea0650a8a84b69b54e0a0a76f862b
Signed-off-by: Zoltan Ujhelyi <[email protected]>

documentation/org.eclipse.viatra.documentation.example/src/org/eclipse/viatra/documentation/example/queries/CPSQueries.vql

@@ -103,6 +103,7 @@ pattern reachableState(sm :StateMachine, state: State){
 // tag::maximumNumberOfInstances[]
 pattern maximumNumberOfInstances(at : ApplicationType, max : java Integer) {
 	max == max find sumNumberOfInstances(at, #);
+	find sumNumberOfInstances(applicationType, max);
 }
 
 pattern sumNumberOfInstances(at : ApplicationType, n : java Integer) {

documentation/org.eclipse.viatra.documentation.help/src/main/asciidoc/tutorial/queries.adoc

@@ -192,7 +192,7 @@ This section introduces a set of more complex queries, useful for both introduci
 
 It is possible to find the Application Type that has the most instances defined in the model by combining a _counting_ of the values of the related feature and a _max_ function.  The `sumNumberOfInstances` helper pattern uses a `count` call of the `ApplicationType.instances` feature (note the omission of the `find` keyword there). This feature is available starting with VIATRA 2.0, and allows reducing the number of trivial helper patterns, like the pattern `hostIpAddress` introduced earlier in this tutorial.
 
-After the counts are available in the match set of a pattern, it is easy to calculate the maximum value using the `max find` construct.
+After the counts are available in the match set of a pattern, it is possible to calculate the maximum value using the `max find` construct. However, it is important that calculating the maximum does not connect the ApplicationType instances to their maximum, that needs to be done with an additional constraint.
 
 [[vql-maximumNumberOfInstances]]
 [source,vql,indent=0]