|
• Relationship: Select this option to add a single-reference relationship (references-one, owned by, scoped-by, or hierarchical parent).
• Attribute: Select this option to add an attribute from an application class.
• Interface class: Select this option to refer to another interface class. Only other custom interface classes will be available for selection. You can use this option to include attributes from a related application class (for example, to include requirements for a work order task).
The type of reference to use for the object at the end of the relationship. For example, if you are entering the WorkRequest.AssetToWorkOn relationship as a property and you select Base class user key as the reference type, the property will contain the Asset number of the work request’s asset.
• Base class user key: A unique name or number used to identify each instance of an object in the base class. Some user keys can be edited by APM users. For example, the user key for an asset is the asset number.
• Object ID: A unique object identification number that is assigned and managed by APM.
• Universal ID: A unique identification number generated by the system. This number will always be the same in both the desktop and remote databases.
Required reference is selected by default. It is sometimes deselected for relationships on inbound interface classes in APM if the referenced object (for example, an indicator state) might not exist. This prevents the upload transaction from failing.