Attribute Description

Enter the name for the attribute in this field. You can enter up to 100 characters, using any combination of letters or numbers. The name you enter here is also used when you add the attribute to a view: It identifies the attribute in the layout palette. It is the default label for the attribute when you drag it onto a view. It is the default column heading for the attribute in a multi-column list box.

	See Also

Member Name

This field enables you to identify the member name of the attribute. The member name is used in the C++ code to identify the attribute, so it cannot include spaces or punctuation. Each attribute within a class must have a unique member name. APM automatically creates a member name based on the attribute description you enter. You can change the member name if necessary.

	See Also

Column Abbreviation

The column abbreviation field is used to create the column name for the attribute in the database. You can accept the default abbreviation, or you can enter up to 12 characters. Each attribute within a class must have a unique column abbreviation.

	See Also

Attribute Type

An attribute can be either a data type or an enumerated type. Data Type: Data types define the type of data that they represent. Dates, prices, quantities, and integers are examples of data types. Enumerated Type: Enumerated types are user-defined data types consisting of a set of named constants called enumerators. For example, if your object requires that the end users enter a day of the week, you can create an enumerated type for days of the week. End users are then restricted to selecting one of the enumerator choices you have defined. If your attribute is an enumerated type, you must identify it in the corresponding Enum Type field. Before you can select the specific enum type, you must have created a new enumerated list.

	See Also

Attribute Length

If you have selected an attribute data type of String or Variable Length String, you need to specify the length of the attribute. The length is expressed in the number of characters allowed in the field. For example, an attribute length of 20 will accept up to 20 letters and numbers. String data types can be from 1 to 255 characters long. Variable string data types can be from 256 to 2000 characters long.

	See Also

Null behavior

Type of message to be displayed at run-time if the user leaves this attribute blank. You have three choices: Mandatory, Warning, and No Message. Mandatory: The following message is displayed when the user leaves this field blank: You must specify the <attribute description>. Warning: The following message is displayed when the user leaves this field blank: You didn’t specify a value for <attribute description>. Continue anyway? Null value allowed: No message appears when the user leaves this field blank.

	See Also

Default Value

This field enables you to indicate the default value of a enum-type attribute.

	See Also

Sequence Number

This field enables you to specify the order this attribute appears in the user key. You only need to enter the sequence if the attribute is part of the user key. Most classes that have a user key have only one component. For example, the user key for a purchase order is usually the purchase order number. When the user key has only one component, it doesn't matter what sequence number you provide. If the user key has more than one component, the sequence number is used only to determine the order, not its absolute position. For example, you could specify a sequence number of 2 for the first component and 4 for the second.

	See Also

Persistable

This check box enables you to indicate whether or not the attribute is persisted to the database. Most of your attributes will be persistable. However, you may wish to define non-persistable attributes from time to time. Non-persistable attributes exist only in memory. Typically, they are calculated from other persistable attributes in business logic. One reason you might define a non-persistable attribute is to include it in the user interface for the class. For example, a sales order might include persistable attributes for the unit price and quantity. The total price of the order would be a non-persistable attribute that is calculated whenever the unit price or quantity change.

	See Also

User Key

This check box enables you to indicate whether or not this attribute is the user key for the class. This option is only relevant if the class that contains this attribute has a user key. A user key is a unique name or a number used to identify each instance of this class. For example, the user key for a Customer object may be the Customer's Name and the user key for a Purchase Order might be the Purchase Order Number. Note that an attribute that functions as a user key must be one of the following data types: • String • Short integer • Long integer • Integer

	See Also

Copyable

This check box indicates whether or not you want the attribute to be copied when an instance of this class is copied. Typically, transaction-oriented attributes, or attributes that you want to set in business logic, are not copied when you copy the object. For example, when copying a purchase order, you probably don't want to copy its “date printed” attribute.

	See Also

Transactional

This check box affects the locking behavior of the attribute. If you indicate that an attribute is transactional, it can be updated even if the object is checked out for editing. For example, suppose you have a Vendor class that has a Year-To-Date Purchases attribute. If you make this attribute transactional, one user could open an instance of a vendor and check it out in order to change the vendor's address, while another user could create a purchase order for this vendor that updates the vendor's year-to-date purchases. Effective use of transactional attributes will help you minimize the number of lockout situations caused by object extensions.

	See Also

Read-Only

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

	See Also

Securable

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

	See Also