GRM rules(Generic Relationship Manager)

GRM rules (Generic Relationship Manager)

Generic Relationship Management (GRM) rules is used to apply constraints on the relationship between two business objects.

Using Generic Relationship Management (GRM) rules we can apply limit what objects can be pasted to other objects.

For example, if you do not want a certain type of object to have a specification relation to another type, you can set the cardinality to 0 to deny pasting of one type of object to another with the specification relation.

When you create a GRM rule, you select the primary business objects and secondary business objects for the relationship, the relationship they have to one another, and the constraints to be applied. 

Available relationships are children of the ImanRelation business object.

Cardinality : Determines the number of allowed occurrences of the primary object in relation to the secondary object, and of the secondary object in relation to the primary object.

When you create a GRM rule, type a number in the Primary Cardinality or Secondary Cardinality, allowed numbers are:

-1 or *                   =     Allow an unlimited number of relationships.

0                            =     Do not allow any relationships.

1, or 2, or 3, and so on    =    Allow the specified number of relationships.

Inheritance of GRM rules

The GRM rule applies for all children of the primary and secondary objects. However, rules defined for a sub-business object take precedence over the relation rules defined for a parent object.

For Example : 

If the ItemRevision business object is chosen as the primary object, and the DirectModel dataset is chosen as the secondary object, then all children of these objects that have the relationship inherit the rule.

Therefore, all instances of the children of ItemRevision that are related by the relation specified in the rule to any instance of children of DirectModel are subject to the constraints defined by the rule.