Designer 10.7 | Centrasite Eclipse UI Help | Tasks | Working with Registry Objects | Versioning Services | Handling of Associations
 
Handling of Associations
When you create a new version of a service, its associations and the corresponding target or source objects are handled according to the following rules. The same rules apply to associations assigned to service bindings and specification links of the service.
Outgoing associations:
*Associations of the following types are NOT copied to the new version of the service, i.e. the new version does not have these associations: BelongsTo, HasParent, EquivalentTo, Extends, Supersedes, user-defined associations.
*Associations of the following types are copied to the new version and linked to the same target object as for the old service version: RelatedTo, ExternallyLinked, InstanceOf, Uses, Replaces, ResponsibleFor, SubmitterOf.
*Associations of the following types are copied to the new version and linked to a copy of the target object: HasChild, HasMember, Contains, Implements. The copy of the target object is created by the versioning operation. If the target object is a versionable object, the copy is represented as a new version of the target object.
Incoming associations:
*Associations of the following types are NOT copied to the new version of the service, i.e. the new version does not have these associations: BelongsTo, RelatedTo, HasChild, HasMember, ExternallyLinked, Contains, EquivalentTo, Extends, Implements, Supersedes, Uses, Replaces, ResponsibleFor, SubmitterOf, user-defined associations.
*Associations of the following types are copied to the new version and linked to the same source object as for the old service version: InstanceOf.
*Associations of the following types are copied to the new version and linked to a copy of the source object: HasParent. The copy of the source object is created by the versioning operation. If the source object is a versionable object, the copy is represented as a new version of the source object.