Page History
Info | ||||
---|---|---|---|---|
| ||||
AQ_Aggregate_Update is used for updating an already created (=stored) aggregate |
Creating and updating aggregates
...
Name | Direction | Description | Type | Occurrence | Required |
---|---|---|---|---|---|
AggregateType | Input | Select the aggregate you want to update. This is a list of the aggregates definitions. | Aggregate | Single valued | trueYes |
AggregateId | Input | The attribute that holds the ID of the aggregate you want to update. | Integer | Single valued | trueYes |
CreateNewVersion | Input | Specifies whether the update creates a new version (true) or overwrites the existing version (false). | Boolean | Single valued | trueYes |
VersionIDOutput | BiDirectional | The attribute on which you want to store the version Id of the update. | Attribute | Single valued | falseNo |
TargetInsance | Input | The instance on which the Id of the version that is to be updated will be stored in the attribute mentioned in VersionIDOutput. | Expression resulting in an attribute | Single valued | falseNo |
StoreInstances | Input | The starting point instance(s) for storing. | Expression(s) resulting in instance(s) | Multi valued | falseNo |
User-set vs system-set
When updating an aggregate, only values that are user-set are stored, all system-set values are not stored. The data of the aggregate is stored in a xml blob.
...
Below an example is given for an update service with versioning.
Service call definition | ||||
Aggregate definition | ER diagram | Service definition |
Visual overview of aggregate concepts
...