The Archiving process introduced with BMC Remedy ITSM 9.0 makes use of the form-level association management capabilities that are available with BMC AR System 9.0. Using association management enables the archiving feature to track and maintain the relationships among the BMC Remedy ITSM application forms.
For detailed information about how the Archiving process is implemented from the BMC AR System platform, follow the link provided in Related topics at the bottom of this topic.
This topic includes the following sections:
Association management in BMC Remedy AR System
An association is a BMC Action Request (AR) System server object that describes relationships between entries in BMC Remedy AR System forms. The association enables you to manage relationships between entries in two forms to support referential integrity, cascade deletes, and archiving related entries.
An association defines a relationship between entries in two forms. The relationship can have three cardinality options: One to One, One to Many, and Many to Many. For one-to-one and one-to-many relationships, an association between two forms is defined by specifying one form as primary and another form as secondary. For these relationships, the primary form can have only one entry in the relationship. For many-to-many relationships, there are no primary and secondary forms.
BMC Remedy AR System associations are used in BMC Remedy ITSM application primarily for archiving. You can also use these associations with RESTful APIs to get related entries. For more information, see Operations on entry objects.
The following sections are provided:
Understanding the value of associations
Associations can be used to describe the data model for an application. You can understand an application easier with associations. Enforced associations can eliminate the need to create workflow to restrict operations or to remove related data when an entry is deleted. Reducing the amount of workflow needed for an application again makes it easier to understand your applications.
Associations can also be used to govern the behavior of archive definitions. For more information, see Defining associations to follow.
Each association has cardinality, which dictates how the entries in the two forms are related. The options are:
- One to One — This cardinality describes a relationship in which an entry from the primary form can be related to exactly zero or one entry in the secondary form.
- One to Many — This cardinality describes a relationship in which an entry from the primary form can be related to zero or more entries in the secondary form.
- Many to Many — This cardinality describes a relationship in which an entry from the primary form can be related to zero or more entries on the secondary form and an entry from the secondary form can be related to zero or more entries on the primary form.
All cardinality options may have an entry that is related to no other entries. For example, a one-to-one relationship between an employee and email address includes the possibility that an employee might not have any email addresses.
Data relationships defined by associations may be enforced (strong) or not enforced (weak).
If an association is defined as enforced, the BMC Remedy AR System server ensures data integrity is maintained. Data integrity means that the server will enforce the cardinality of the association and will ensure referential integrity. Thus, an entry will not be able to refer to another entry that does not exist.
Associations enforced on forms are also enforced on the archives of those forms.
Only one-to-one and one-to-many cardinality can be enforced. You cannot create an enforced many-to-many relationship in BMC Remedy AR System. The server performs the following functions for the enforced association:
- If an entry is deleted from the primary form, the server deletes all related entries from the secondary form (cascade delete).
- Server does not allow duplicate primary key values in the primary form. For example, each employee must have unique ID.
- Server does not allow entries in the secondary form with invalid foreign key values. For example, an entry in the contact form must reference a valid employee.
- Server does not allow changing primary key values in the primary form if they are referenced in a secondary form. For example, you cannot change an employee ID if that employee is referenced in a birth information form.
- For one to one associations, the server does not allow creation of entries in the secondary form if that breaks the cardinality defined by associations. For example, it will not allow creation of a second birthday entry for the same employee.
If an enforced association is created between forms that already contain data, it is not necessary that the existing data should have referential integrity. However, any changes to the data after the association is created will follow enforcement and should have referential integrity.
If an association is not enforced, the BMC Remedy AR System server allows creation of records even if the creation breaks the cardinality defined by the association or the referential integrity. If an association is not enforced, the server does not perform the actions listed above for enforced associations.
Unenforced associations provide a way to describe data relationships that are not directly enforced by the server. These associations may be otherwise enforced, by defining workflows in BMC Remedy Developer Studio.
Type of associations
Entries in forms may contain direct references to each other, or may be related through a third form that contains references to each of the related entries. The association type describes which of these approaches is used.
Can be Enforced?
One to One
One to Many
Direct associations are primary key and foreign key associations between two forms.
Multiple fields from main form can be used as a primary key and similarly multiple fields from the secondary form can be used as a foreign key. In other words, each field of the primary key maps to a field in the foreign key and is called direct association.
One to One
One to Many
These types of associations are called external associations where the associations are created by using a third form. This third form, called an association form, stores the foreign key for both the primary and secondary forms. Multiple fields from the primary form can be mapped to the same number of fields on the association form and similarly multiple fields from the secondary form can be mapped to the same number of fields on association form.
|Many to Many||No|
Direct associations involve only two forms, and require that references from one form to the other use only data that is present on the forms. Direct associations can be used for one-to-one and one-to-many relationships. They cannot be used for many-to-many relationships. In the following example, the Employee Phone form directly holds reference to Emp ID of the Employee form.
|Emp details||Emp ID||Emp ID||Phone details|
Indirect associations include a third form that contains references to each of the related forms. Entries in the two related forms in an indirect association do not have references to each other. Indirect associations can be used for any kind of relationship, and only an indirect association can be used for a many-to-many relationship. In the following example, the Employee-Department form (third form) contains references to the two related forms: Employee and Department.
Whether the association is enforced or not, for an indirect association, the server will always delete related entries from association form if an entry is deleted either from primary or secondary form.
|Emp details||Emp ID||Emp ID||Dept ID||Dept ID||Dept Info|
When defining an association, you have the option of specifying a qualification for each of the forms involved. Qualifications allow different relationships between entries in the same two forms or the storage of multiple relationships in a single indirect association form.
When you specify qualifications, only entries matching the qualification are related to the association. For example, you might have a Phone details form that includes a Phone Type field indicating that an entry is an office phone number or another type of phone number. You could then create different associations between an employee form and the phone details form:
- one-to-one association between an employee and an office phone
- one-to-many association between an employee and all other phones
You would add a qualification in the first association requiring that the field on the telephone number form be office phone option.
An Association object does not have any permissions. Only administrators are allowed to create, modify and delete associations. All other users can view an association, if they have access for viewing the all the fields and forms used in that association.
The following topics provide you with information about how the Archiving process is implemented from the AR System platform. Make sure you read and understand these topics if you need to customize the Archiving process behavior or need to implement archiving on customized forms.
- (In the BMC Remedy AR System documentation space. This is a top level topic that introduces archiving in BMC Remedy AR System and provides links to other, relevant BMC Remedy AR System archiving documentation.)
- Managing the Archiving process policies