Relationships

IBM® Rational® Synergy uses relationships to relate one object to another object within a database.
Relationships are maintained as follows:

The term object means versioned objects. The term object also means any object that is stored in a Rational Synergy database. For example, projects, folders, tasks, and change requests.

Each relationship has a name. Relationship names can be any combination of alphanumeric characters. The name of a relationship identifies the nature of the relationship. Examples of relationship names include successor, task_in_folder, and associated_task.

A relationship is unidirectional. It points from one object to another object. For example, if cosine.c-2 is the successor of cosine.c-1, the successor relationship points from version 1 to version 2. You can access the relationship from either object. For example, you can find that version 1 has successor version 2, and that version 2 is a successor of version 1.

An object can have any number of relationships. It can have many instances of the same relationship, with the same name, to different objects. For example, a single problem can have many associated tasks. An object can be on either end of a relationship. For example, an object can have a successor object and be a successor to another object. An object can have many different types of relationships. For example, a task can be in a folder (task_in_folder), associated to source objects (associated_cv), and related to another task that fixes it (fix).

When you delete an object that has relationships, Rational Synergy automatically deletes the relationships to and from that object.


Feedback