Creating Fields for Request Types

You use the Field window to create and configure request type fields. From the Field window, you can specify:

  • Whether the field is hidden displayed

  • Whether the field is editable under specific circumstances

  • Default field values

  • Dependencies tied to values of other fields in the request type

To create a request type field:

  1. Log on to PPM.

  2. On the Open menu, click Administration > Open Workbench.

    The PPM Workbench opens.

  3. On the shortcut bar, click Demand Mgmt > Request Types.

    The Request Type Workbench opens.

  4. Open a request type.

    The Request Type window opens to the Fields tab.

  5. Click New.

    The Field: New window opens to the Attributes tab.

  6. In the top section of the Field window, provide the information described in the following table.

    Field or Option

    *Required

    Description

    *Field Prompt

    Type the label for the request type field for display on the request details page.

    *Token

    Type an uppercase text string to use to identify this field. The token name must be unique for the specific request type (for example, ASSIGNED_TO_USER_ID).

    Note: If you add a table component field and the table component field contains an ACL column, you cannot set the token to numbers only. Otherwise, PPM would throw exceptions when you click the ACL in the request details page.

    Description

    (Optional) Type a short description of the field.

    Enabled

    If you do not want the field enabled for this request type, click No. Otherwise, leave Yes selected.

    *Validation

    Use the auto-complete to specify the validation for this field. The validation determines what type of component this field is to be (plain text field, date field, drop-down list, and so on) and what values are valid for the field. For more information on validations, see the Commands, Tokens, and Validations Guide and Reference.

    Note: When you specify the validation, make sure that the token(s) referenced by the validation already exist.

    Multi-Select Enabled

    If you selected an auto-complete component for the validation, and you want to allow users to select more than one value, then click Yes.

    If you selected a non-ACL component for the validation, users cannot select more than one value, regardless of whether or not the Multi-Select Enabled option is enabled and whether or not its value is Yes. This also applies to Web services.

    Note: Some header fields do not allow the multi-select option.

  7. On the Attributes tab, provide the information described in the following table.

    Attribute Name

    Description

    Section Name

    From this list, select the request detail page section that is to display the field. This field is only available if you have created two or more sections to display for requests of this type.

    For instructions on how to create sections, see Adding Sections to Request Types

    Display Only

    To make the field read-only, and uneditable even at initial request creation, select Yes.

    Transaction History

    To turn on transaction auditing for this field, select Yes. Whenever the value in this field changes in a request, that change is logged to a transaction history table.

    Notes History

    To turn on notes auditing for this field, select Yes. Whenever the value in this field changes in a request, the change is logged in notes for the request.

    Display on Search and Filter

    To prevent the field from being displayed on Search and Filter pages in the standard interface, select No.

    Display

    To prevent the Request Type field from being displayed for requests of this type, select No.

    Note: If you select No, no matter what you select for Display Only, the field is hidden.

    Search Validation

    Use the auto-complete to specify the logic to use to determine the valid search values in this field.

    Note: The total number of fields in a request type cannot exceed 359 if you enabled any one of the following attributes in any field:

    • Notes History

    • Transaction History

  8. Click the Default tab.

  9. Provide the following information:

    1. To specify that the field is to have no default value, in the Default Type field, leave None selected. To specify that the field is to have a constant as the default value, select Constant.

      You can also configure a default value that is based on the value in another field or derived from a parameter. To configure these default types, you configure a rule or a command to automatically populate the request type field. For instructions on how to do this, see Request Type Rules and Configuring Commands for Request Types .

    2. If you selected Constant as the default type, then in the Visible Value field, type the constant value.

  10. Click the Storage tab.

    On the Storage tab, the field is automatically placed into the next available position within the database based on the current field attributes. To locate a field in the database, an administrator can open the Field window for a specific field in a request, and use the Storage tab. This is useful for reporting purposes.

    If necessary, you can use the Storage tab to specify a field location within the database when creating a new field. However, the standard practice is to allow the interface to automatically position the field for the administrator.

    The Storage tab automatically stores the value for a text field that has a maximum length of 4000 characters in column 41 or higher.

  11. Provide the following information:

    1. From the Max Length list, select a value to set the maximum number of characters for the field value (either 200 or 4000).

    2. From the Batch Number list, select the batch number for the field.

      Note: Batch number is based on the number of maximum fields. For every 50 fields, one batch is created. 10 Ten of these the 50 fields in a batch can be contain more than 200 characters in length characters. Enabled This list is enabled only when if there are more than 50 fields (creating more than one batch).

    3. From the Parameter Col list, select the internal database column that in which the field value is to be stored.

      Note: These values are stored in the corresponding column in the request details table for each batch of the given request type. Information can be stored in up to 50 columns using request type, allowing up to 50 fields per batch. No two fields in a request type can use the same column number within the same batch.

  12. Click the Security tab.

    The Security tab displays the information described in the following table.

    Field Name

    Description

    Visible To

    Lists all users, security groups, and linked tokens to which the field is visible. By default, the field is visible to all users.

    Editable By

    Lists all users, security groups, and linked tokens for which this field is editable. By default, the field is editable for all users.

  13. To change the default field security settings for the field:

    1. Click Edit.

      The Edit Field Security window opens.

    2. To control who can view the field:

      1. Clear the Visible to all users checkbox.

      2. In the Select Users/Security Groups that can view this field list, select Security Group, User, Standard Token, or User Defined Token.

      3. Use the auto-complete to select the security group, user(s), or token.

    3. To assign your selection editing rights in addition to viewing rights to the field, leave the Provide Editing Rights checkbox selected.

    4. To add the selection to the list of users and security groups who can view the field, click the Add arrow.

    5. To hide the field from a selected security group, user, or token now listed on the right, clear the Visible checkbox in the corresponding row.

    6. To make the field read-only for a selected security group, user, or token, clear the Editable checkbox in the corresponding row.

    7. To remove field access rights entirely, select the user, security group, or token, and then click Remove.

    8. After you finish configuring field security, click OK.

    The Security tab is updated with the list of users, security groups, and tokens with viewing or editing rights to the field.

If you add field-level security to fields on a request type that has been used to create requests, the PPM database tables are updated with this new configuration. Because of the scope of database changes, you must collect database schema statistics. For information about how to collect database schema statistics, see the Installation and Administration Guide. For help with this task, contact your system administrator.

Note: There can only be 500 rows per column, three columns per tab, and a maximum of 20 tabs for each request type.

When taking advantage of the reporting meta layer functionality, those fields contained within the first four batches (200 fields) are available for reporting.