Change Capture for Version Control › Actions on Aggregate Objects Causing Them to be Marked Changed

Actions on Aggregate Objects Causing Them to be Marked Changed

The basic changes that cause an object to be marked as changed are as follows.

• Add an Object—If an object is added and it is an aggregate object, the object itself is marked as changed. If a non-aggregate object is added, its parent aggregate object is marked as changed.
• Delete an Object—Deleting an object involves dissociating two objects; see Remove an Association between Two Objects.
• Modify Object Type—If an object type is modified and it is an aggregate object, the object is marked as changed. If a non-aggregate object's type is modified, its parent aggregate object(s) are marked as changed.
• Update Property of an Object—If an object's property is updated, and it is an aggregate object, the object is marked as changed. If a non-aggregate object's property is updated, its parent aggregate object(s) are marked as changed.
• Add an Association between Two Objects—If you add an attribute to an entity, that association causes the entity to be marked as changed. Any time an association is created between two objects, a change to an aggregate object is marked.
• Remove an Association between Two Objects—If you remove an attribute from an entity, the deletion of that association causes the entity to be marked as changed. Any time you delete an association between two objects, a change to an aggregate object is marked.
• Move/Reorder an Association between Two Objects—If the order of attributes of an entity is changed, the entity is marked as changed. Any time an association is moved between two objects, a change to an aggregate object can be marked.