Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AQ_Aggregate_Search retrieves the Aggregate Id(s) belonging to the found aggregates and stores this in an attribute, ready for use by (for example) Service call type: AQ_Aggregate_Read.

Service call definition:
Image Added

Aggregate definition:
Image AddedImage Removed


Parameters

Parameter
Direction
Value
Description
Required
Aggregate typeInputModule element AggregateSelect the aggregate type to search.TrueYes
Target entityOutputEntity

Select an entity in which you want to store the aggregate ID and version.

If this entity is a singleton, no instances will be created and the next two parameters will be used to contain Id and version of the found aggregates.

If this entity is a multiton, an instance is created for each found aggregate and the next two parameters will contain single values.

Note

Instances of the specified multiton are deleted before the search is run. Each search is performed with a clean slate.

TrueYes
Target attribute for aggregate IdOutputAttribute of target entitySelect an attribute of the target entity on which attribute you want to store the found aggregate Id.
This attribute can be singlevalued or multivalued.
TrueYes
Target attribute for version IdOutputAttribute of target entity

Select an attribute of the target entity on which attribute you want to store the found version Id.
This attribute can be singlevalued or multivalued.

FalseNo

Only search for latest versionsInputCheckbock, checked by defaultCheck when only latest versions of versioned aggregates are searched.FalseNo
Maximum resultsInputIntegerThe maximum number of results, the system will stop after reaching this number.FalseNo
Search criteriaInputStandard and custom metadata fieldsSpecify the search criteria, based on standard and custom metadata fields.TrueYes
UI Text Box
typewarning
When searching for aggregates with versions, placing the found aggregate Id's in a multivalued attribute of a singleton and placing the found version Id's in another multivalued attribute of that singleton results in an information gap: it cannot be reproduced which version Id's belong to which aggregate Id's. Therefore, it is possible to let Blueriq create an instance for each found aggregate. See How to search for aggregates.

...