Class

The name of the class to which you are creating a new relationship. You can create relationships to standalone custom classes or to existing APM classes. A standalone custom class has a unique name; it does not add to a class shipped with APM.

	See Also

Type of Relationship

APM enables you to create relationships of the type References One from a custom class to a standalone custom class or to an existing APM class. A standalone custom class has a unique name; it does not add to a class shipped with APM. The References One relationship links to one instance of the other class. For example, the link from work order to the employee who requested the job is a References One relationship.

	See Also

UI Text

The default text that appears whenever this relationship is added to the user interface. This text should describe the purpose of the relationship so end users will know what to select. For example, the UI text “Requestor” describes the References One link from work order to the employee who requested the job.

	See Also

Method Name

This field enables you to specify the string that will be used by the code generator to construct the method names that are associated with the relationship. Whether or not this field is relevant depends on the type of relationship you are defining.

	See Also

Column Name

This field enables you to identify the name of the database column that will contain the object ID of the referenced object. Whether or not this field is relevant depends on the type of the relationship you are defining. APM automatically enters the column name based on the method name you enter, but you can change the column name if necessary. For example, if you are defining the relationship A references B, then you must specify the name of the column in the table for A that will contain B's object ID. If on the other had, you are defining the relationship B is referenced by A, the column name is irrelevant because B's table does not contain a reference to A.

	See Also

Persistable

This check box enables you to indicate whether or not the relationship is persisted to the database. Most of your relationships will probably be persistable. Non-persistable attributes exist only in memory; they are not saved in the database.

	See Also

Read-Only

This check box indicates whether or not you want the relationship to be read-only in the user interface. If the relationship is read-only, the end user will not be able to enter or change it.

	See Also

Copyable

This check box indicates whether or not you want the relationship to be copied when an instance of this class is copied.

	See Also

Securable

This check box indicates whether or not you can secure this relationship in security profiles. If you cannot secure the relationship, all users will have the same ability to view and change it.

	See Also

Transactional

This box shows whether or not you want to be able to change the related class without first getting a long lock on the object. This option is irrelevant if the column name is blank. If you indicate that a relationship is transactional, it can be updated even if the object is checked out for editing.

	See Also

Message if Blank

The type of message that is displayed if the user leaves this relationship blank. Your options are: Mandatory: The following message is displayed if the user leaves this field blank: You must specify the <UI text>. Warning: The following message is displayed if the user leaves this field blank: You didn't specify a value for <UI text>. Continue anyway? Null allowed: No message appears if this field is blank.

	See Also

Layout Palette

This check box indicates whether or not you want the relationship to appear in the layout palette. The layout palette is used to design the user interface; if the relationship does not appear in the layout palette, then you cannot include it on the user interface.

	See Also