Creating Object Type Fields

To create an object type field:

1. From the Workbench shortcut bar, select Deployment Mgmt > Object Types.

   The Object Type Workbench window opens.

2. Open an object type.

   The Object Type window opens.

3. Click New.

   The Field window opens.

4. Complete the fields in the Field window as specified in the following table.

   Field Name	Description
   Field Prompt	Type the name of the new field.
   Token	Type a unique name for the token.
   Description	Type a description of the new field.
   Enabled	Select Yes to make the field available to the system.

5. Select a Validation.

   See Overview of Object Type Field Validations for information on choosing a validation. If no existing validation meets the requirements, create one that does.

6. Configure field behavior.

   This consists of setting options in the field's Attributes, Default, and Dependencies tabs. Note that some field behavior is dependent on other object type fields. You may need to revisit this step after you create the other fields in the object type.

   To configure field behavior:

   1. Complete the fields in the Attributes tab, as follows:

      Field Name	Description
      Parameter Col.	Indicates the internal database column that the field value will be stored in. These values are stored in the corresponding column in the package lines table for each line of the given object type. Information can be stored in up to 30 columns to allow for up to 30 fields/parameters. No two fields in an object type can use the same column.
      Display Only	Indicates whether to display a field using the following options: Always Never Use Dependency Rules Select Use Dependency Rules to use the logic defined on the Dependencies tab.
      Display	Indicates if this field is visible in the package line region of the package window.
      Required	Indicates if a value needs to be specified for this field using the following options: Always Never Use Dependency Rules Select Use Dependency Rules to use the logic defined in the Dependencies tab.
      Editable	After a package line has been typed and submitted, it starts moving through its workflow. This attribute determines if the field can still be updated. For example, it may be necessary to ensure that a Filename field is not editable after package lines of file object type start getting processed.
      Notes History	Notes stored for historical purposes.

   2. Complete the fields in the Default tab.

      Field Name	Description
      Default Type	Determines whether the field has a default value. Either default the field with a constant value, default it from the value in another field, or default to a parameter.
      Visible Value	If a default type of constant is selected, type the constant value here.
      Depends On	If defaulting from another field, type the token name of that field. At runtime, when using this object type, every time a value is typed or updated in the source field, it is automatically typed or updated in this destination field.

   3. Complete the fields on the Dependencies tab. You must have selected the Use Dependency Rules from the Attributes tab.

   Field Name	Description
   Clear When The Following Changes	Indicates that the current field is to be cleared if the specified field changes.
   Display Only When	Indicates that the current field is to be editable only if certain logical criteria are met. This field functions with the following adjacent fields: A list containing the logical qualifier A text field
   Required When	Indicates that the current field should be required when certain logical criteria are satisfied. This field functions with the following adjacent fields: A list containing logical qualifier A text field

7. Click OK.

   The changes to the object type are saved.