Conditions can often be complex to write, involving navigation across several relationships to get to the information required. This is not only administration overhead but also can introduce performance overhead. By exposing and configuring any related items as properties on an object, you can use the properties to specify conditions that are simpler to write and maintain and to speed the display of shortcut menus.
End1PropertyForEnd2Name and End2PropertyForEnd1Name are properties on a relationship definition used to propagate data between the objects on either end. End1PropertyForEnd2Name stores the name of the object on End2 for use as a property on the End1 object. The End2PropertyForEnd1Name stores the name of the object on End1 for use as a property on the End2 object.
RelDefPropagatesTo is a relationship definition that can be used on complex objects. It creates a relationship between two relationship definitions to propagate the relationship from a parent object to a child object. When RelDefPropagatesTo exists on a relationship definition, the PropagateRelationship method propagates this relationship from the parent object to any child objects. By default, these properties and relationship definitions are configured to propagate the value of the originating organization relationship into the OriginatingOrgName property. The OriginatingOrgName property holds its end object name or its parent object’s OriginatingOrgName property value. This property is exposed on IObject.
When a relationship is created, or updated for any object, the software checks if RelDefPropagatesTo exists on the relationship definition. If RelDefPropagatesTo exists, it propagates that relationship to its children. It also checks if End1PropertyForEnd2Name and End2PropertyForEnd1Name are set on the relationship definition. If the properties are set, the property value is stored on the other end object's property.
For example, on a transmittal, the SPFCFromInternalOrg relationship definition can be configured so that the name of the From organization is stored on the transmittal object. Since organizations control many objects, such as transmittals, documents, tags, and more, the out-of-the-box environment is configured to write the organization onto a property on IObject.
Exposing the organization property makes it simpler to write conditions to navigate between objects and makes it faster for the system to evaluate these conditions. An example of a condition that is easier to evaluate is: Obj.OriginatingOrgName = Env.USERORGANIZATIONNAME.
The three scenarios show when the property is set. The RelDefPropogatesTo relationship definition exists between SDADocOriginatingOrg and SDADocRevOriginatingOrg to propagate the relationship from the master to the revision. Because this relationship exists, the ProgagateRelationship method propagates the relationship to the child objects.
Scenario 1
Updating the SDADocOriginatingOrg relationship does the following:
-
Sets the OriginatingOrgName property on the document master.
-
Synchronizes the relationship to the SDADocRevOriginatingOrg property.
Updating the SDADocRevOriginatingOrg relationship does the following:
-
Sets the OriginatingOrgName property on the document revision and version and on the file object.
Scenario 2
Updating the SDADocOriginatingOrg relationship does the following:
-
Sets the OriginatingOrgName property on the document master.
-
Does not synchronize the relationship to the SDADocRevOriginatingOrg property because the RelDefPropogatesTo relationship definition does not exist.
-
Does not set the OriginatingOrgName property on the document revision because another relationship definition exists to control it.
Updating the SDADocRevOriginatingOrg relationship does the following:
-
Sets the OriginatingOrgName property on the document revision and version and on the file object.
Scenario 3
Updating the SDADocOriginatingOrg relationship does the following:
-
Sets the OriginatingOrgName property on the document master, revision, and version and the file object because the revision relationship is not set to propagate the organization property.
-
Does not synchronize the relationship definition because the RelDefPropogatesTo relationship definition does not exist.