Page History
...
If the attribute selected for the AggregateId is not part of a singleton then the target instance parameter can be used to select the instance on which the aggregate Id must be stored. If the target instance has no value, then it is assumed that the selected attribute either belongs to a singleton entity, or that there is an active instance present. If not, an error is thrown. The target instance must be single valued.
Parameters
Name | Direction | Description | Type | Occurrences | Required |
|---|---|---|---|---|---|
| AggregateType | Input | Select the aggregate you want to create and store. This is a list of the aggregate definitions. | Aggregate | Single valued |
| Yes | ||||
| AggregateId | Output | The attribute on which you want to store the created aggregate Id. | Attribute | Single valued |
| Yes | ||||
| TargetInstance | Input | The instance you want to use for storing the aggregate Id. | Expression resulting in an instance | Single valued |
| No | ||||
| VersionIDOutput | Output | The attribute on which you want to store the version Id of the created aggregate. | Attribute | Single valued |
| No | ||||
| StoreInstances | Input | The starting point instance(s) for storing. | Expression(s) resulting in instance(s) | Multi valued |
| No |
User-set vs system-set
When storing 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 a create service with versioning.
Service call definition
| |
Aggregate definition
| |
ER diagram
| Aggregate definition
|
Service definition | |
Visual overview of aggregate concepts
...
Overview
Content Tools