Using aggregate objects lets you identify objects that have changed and must be transferred between family members. Each aggregate object in a model represents a collection of related objects in much the same way that a scoping object does in subsetting. Although similar in some ways, aggregate objects and subset scoping objects have important differences.
Version control can define smaller, more specific expansions than subsetting. For example, version control can migrate an object as small as a single attribute, whereas to check out an attribute, subsetting must scope the entity type that owns the attribute.
The ability to define smaller, more specific expansions is an example of granularity. Version control is more granular than subsetting. The context requirement of version control is less stringent because the sole purpose is to transfer objects from one model to another.
For a list of aggregate objects that can be migrated, see Aggregate Objects for Migration.
An aggregate object can have three parts:
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|