The Dependencies tab displays the relationships of the selected element to other elements in the model. Dependencies can be created implicitly, for example, by referring to an element in logic. Alternatively, Lookup type dependencies can be created by adding elements directly to this tab.
Dependency relationships are described in terms of a client, the element defining the dependency, and a supplier, the element the client depends on.
Depends on
This list displays the elements on which the selected element depends.
The following table shows the dependency relationships that might be displayed for selected elements:
| Dependency | Type | Client | Supplier | Description |
|---|---|---|---|---|
| Key | Profile Parameter | Attribute | Defines the ascending or descending order of persistent attributes that act as keys to a profile. Key dependencies become members of their client. | |
| Auto | Lookup | Ispec | Attribute | Ispec classes can be defined to automatically look up other classes based on the values of one or more of their attributes. This dependency can be added manually on the Dependencies tab. |
| Auto | Persist | Event | Attribute | The client persistent attributes are made to persist in an attribute of another class. The dependency is valid when all persistent attributes of the client are keyed to persistent attributes of the supplier. A client can have only one Auto Persist dependency. Specifying the Auto Persist property for the selected event sets this dependency. |
| Use |
| Method | Object | Identifies the usage of an object within a logic statement. A Use dependency becomes invalid when the supplier is modified after the dependency is created. |
Lookup dependencies
Lookup dependencies for ispecs are the only dependencies that can be manually added to this list:
Right-click any where in the list and select Add Lookup.
Select the required attribute in the Dependency Picker.
Click OK.
The unresolved keys are also displayed in the list for the Lookup dependencies.
To rectify the unresolved keys, perform the following:
Select the unresolved attribute in the Depends on list.
Select the required client attribute using the Element Picker in the Properties window.
Click OK.
AutoLookUp Properties
The table below lists all properties for the LookUp dependency.
|
Property |
Function |
|---|---|
| Client | Read-only. Identifies the dependent element. Reflected as the ‘Source’ column on the Dependencies tab. The following elements can only be defined as Client and the elements must have their Presentation Type property set to a value other than None:
|
| Description | Specifies a short description of the selected element. |
| IfPresent | Specifies whether to look up the object if the value for the key is defined. If set to True, the profile becomes conditional and returns a view instead of an index. Note: This property becomes visible only when a key is selected. |
| Kind | Read-only. Identifies the kind of element selected. |
| Supplier | Read-only. Identifies the element that satisfies the dependency. Reflected as the ‘Target’ column on the Dependencies tab. The following elements can only be defined as Supplier and the elements must contain attributes that are defined as keys:
Note: The ‘Event’ and ‘CopyEvent’ elements cannot be defined as Supplier as these elements cannot contain a keyed attribute. |
| Status | Specifies whether the dependency is valid. |
Depended on by
This list displays the elements that are dependent on the selected element. It is for display purposes only. Elements cannot be added or deleted from this list.