Page History

In many situations, end users are interested in statistics about aggregates.
For instance, regarding all person-aggregates, how many men and how many women are currently present?

To make this possible, the container AQ_Statistic_Aggregate is available. This The AQ_Statistic_Aggregate container will provide statistics about aggregates and always result in an a positive integer (zero or more0, 1 ,2 etc).
Multiple containers of this type can then be , that can be used together with in the container Container type: AQ_StatisticsStatistic_Visualization [9.6]

Finding an aggregate means that the Id is not known at the moment, retrieving it means that the Id is known and the aggregate can be read from the aggregate database directly.
However, when an end user enters an application (or logs in), the application may not know which aggregates belong to or are applicable for this end user.

Therefore, the AQ_Aggregate_Search service is available, that finds aggregate Ids, given one or more parameters.

Screen

Image Removed

Configuration screenshot

Image Added

Parameters

Parameter		Direction	Value	Description	Required
Aggregate type		Input	Module element Aggregate	Select the aggregate type to

searchTrueTarget entityOutputNon-singleton entitySelect an entity for which you want to create an instance for each found aggregateTrueTarget attribute for aggregate IdOutputAttribute of aforementioned entitySelect an attribute of the aforementioned entity on which attribute you want to store the found aggregate IdTrueTarget attribute for version IdOutputAttribute of aforementioned entitySelect an attribute of the aforementioned entity on which attribute you want to store the found version Id

False

Only search for latest versionsInputCheckbock, checked by defaultCheck when only latest versions of versioned aggregates are searchedFalseMaximum resultsInputIntegerThe maximum number of results, the system will stop after reaching this numberFalseSearch criteriaInputStandard and custom metadata fieldsSpecify the search criteria, based on standard and custom metadata fields

create a statistic for.	Yes
Search criterium line		Input	Line	Create lines for each condition.	Yes
	SearchCriteria	Input	Standard metadata or Custom metadata	Choose between the two types of metadata fields.	Yes
	Metadata	Input	Standard or Custom metadata field	The field that is part of the search criterium.	Yes
	Operator	Input	See table below	The operator that connects the field and the value.	Yes
	Value	Input	Expression	The expression used in the search criterium.	Yes

True

Search criteria

The search criteria are all triples that adhere to the pattern <metadata><operator><value><MetadataField><Operator><Value>. The value can be single or multi, depending on the operator. See the list below.

Operator	Used with metadata of type	Value can be
Equals	All single-valued datatypes	Single value
Not equals	All single-valued datatypes	Single value
Less than	All single-valued datatypes	Single value
Less than or equals	All single-valued datatypes	Single value
Greater than	All single-valued datatypes	Single value
Greater than or equals	All single-valued datatypes	Single value
Like	String	Single value
Not like	String	Single value
In	All multivalued datatypes	Multivalued
Not in	All multivalued datatypes	Multivalued

Events

This service uses two events for a commit and one for an exception:

FoundNoAggregates: typically this node will go to a page with a not-found-message and is of type Rollback.
FoundOneAggregate: typically this note will continue in flow with the found aggregate and is of type CommitSkipSkipValidate (default exit).
FoundMultipleAggregates: typically this node will result in an aggregate list containing all found aggregates and is of type CommitSkipValidate.

Tracing

...

When these containers are placed within Container type: AQ_Statistic_Visualization, the result in runtime looks like this in the Runtime:

Image Added

Space shortcuts

Page tree

Versions Compared

Old Version 2

New Version Current

Key