Using Business Objects

Type a unique name for this object. The name will be stored in the database.

Type a unique display name for this object. This name will appear to users in the Service Desk Console.

Enter a brief description of the purpose of the business object.

Click Add , then from not set, choose a customer type (Contact, Entity, or Identity).

Optional. Choose a form from the drop-down list. You can't choose a form until you have at least one form created. See Using Forms.

Uniquely identifies the definition record.

• You must have one and only one Primary Key field per object.
• The field must contain a value (NULLNo value. A field that is blank. is not allowed).
• The values must be unique.

RecID is set as the default Primary Key field.

Check if the object is part of a clustered index at the database level. Clustered indexes can greatly increase overall speed of retrieval, but usually only where data is accessed sequentially in the same or reverse order of the clustered index, or when a range of items is selected.

This is the same as a clustered index function for a SQL database.

Choose a field to be shown with this business object. For example, you could select CreatedBy to be shown in conjunction with the incident business object.

Select the field to be used for driving the lifecycle of the processes in the business object. When the object is assigned a certain status, for example, certain business rules might be executed.

Choose a field from the drop-down list to facilitate the extension of the business object. A field must be selected to permit an object to be extended.

Check to show this business object in the Common Objects area of the main Business Objects page.

When working with a object derived from the Configuration Item (CI) and FRS_CIComponents objects, check to allow its Configuration Baseline attributes to be copied.

Type a unique name for this index.

Type a useful description for this index.

Check to designate this value as unique, preventing duplicate entries in the index and its backing table. You can create uniqueness by using multiple fields. This option automatically creates an unique index of this field.

Unlike the Primary KeyA type of field that contains a unique value to differentiate this record from all others. You must have one and only one primary key field for each object. By default, this field is RecID. This field must always contain a value and cannot contain a NULL value. HEAT follows Microsoft SQL rules for primary key fields. field:

• You can have multiple Unique fields in the object.
• This field is allowed to contain NULLNo value. A field that is blank. values (although the NULLNo value. A field that is blank. values are not indexed).

The original field you chose appears. Click Add , then choose another field from the list to add more fields. Repeat as needed.

• Under Order, choose the order in which you want the fields sorted: Ascending or Descending.
• Check Included to designate this field as non-key. This is the same as designating a column as INCLUDED within a SQL database. This field is included in the Cover indexAn index that contains all columns needed for a query. A search typically use indexes to speed up the resolution of which rows to retrieve, but then will go to the full table to retrieve the rows., which is used to increase search performance. You must have at least one field NOT checked Included. See the glossary on Included fieldsIncluded fields are non-key fields, which means that they are not indexed and can be sorted in order of importance (as opposed to alphabetically). Included fields are included in a cover index, which helps to speed up searches without slowing down the database. Included fields can have data types not allowed in index key fields..

See Indexing on how this option can affect performance.

Enter a name for the member object, relative to the group object.

The default display name (objectname.suffixname) is generated by the system.

Describe the object.

Optional. Select a form from the drop-down list.

Uniquely identifies the definition record. FrontRange Solutions recommends using this value.

You can enter any other available field in the business object as an identifier as long as it is mandatory and unique.

RecID is the default field.

Select this option if the object is part of a clustered index at the database level. Clustered indexes can greatly increase overall speed of retrieval, but usually only where data is accessed sequentially in the same or reverse order of the clustered index, or when a range of items is selected.

Consult your database administrator for guidance on using this feature.

Select a field to be used as the display name with this business object. For example, you could select IncidentNumber to be displayed in conjunction with the incident business object.

Select the field to be used for driving the lifecycle of the processes in the business object. When the Object is assigned a certain status, for example, certain business rules might be executed.

Select a field from the drop-down list to facilitate the extension of the business object. A field must be selected to permit an object to be extended.

Select this option to show this business object in the Common Objects area of the main Business Objects page.

A unique name for this object. The name is stored in the database.

A unique display name for this object. This name appears to users in the Service Desk Console.