Request Type Components and Configuration Options

Request types have several categories of configurable components. All of these can be viewed and configured from the Request Type window.

The main components of a request type are as follows:

  • General information. General information includes basic request type data such as the name and request type category. For detailed information on these component and how to configure them, see Configuring General Information for Request Types.

  • Fields. Every request type is associated with a request header type that defines a set of fields (such as Priority, Submitted By, and Assigned To) for the request type. You can use the Fields tab to view these default request header type fields and to create additional fields for the request type. For detailed information on request type fields and how to configure them, see Creating and Configuring Request Type Fields.

  • Layout. After you create all of the fields for a request type, you can use the Layout tab to configure their display on request details pages. For information about how to configure the field layout for a request type, see Configuring Layouts for Request Types.

  • Display Columns. Use this tab to configure the request type columns that are available for display in portlets. For instructions, see Configuring Display Columns for Request Types .

  • Request Status. A request usually acquires different status values as it progresses along its workflow. You can set up these status values to drive field behavior, by linking workflow processes to specific information in the request. For information about how to work with request statuses, see Configuring Request Statuses for Request Types .

  • Status Dependencies. The different status values that a request acquires as it progresses toward resolution can be used to control field behavior. For example, a read-only field can become editable following changes that affect request status. For more information, see Configuring Request Field Status Dependencies.

  • Rules. Use this tab to configure request rules that can drive simple or complex interactions between fields in a request. For example, you can configure a rule to set up the automatic population of fields based on dependencies. For more information, see Request Type Rules.

  • Commands. Use this tab to control certain behavior of request type fields. At specific workflow execution steps in a request tracking and resolution process, you can select to run the commands stored in the request type. These commands can then manipulate the data inside a request type field.

    For example, you can construct a command to evaluate several parameters, and then set a default value for the field based on those parameters. This provides an advantage over the defaulting features on the Field tab, which can only default based on a single parameter stored in the same request type. For detailed information on how to set up commands for request types, see Configuring Commands for Request Types .

  • Sub-Types. Use this tab to create valid subtypes for the request type. For example, a defect request type might have hardware, software, and documentation subtypes. For more information, see Configuring Sub-Types for Request Types .

  • Workflows. Use this tab to specify which workflows can be used with a request type. For instructions, see Configuring Request Types to Work with Workflows.

  • User Access. Use this tab to set up rules that govern which users can access requests of this type. (The set of users who can access a request is referred to as request participants.) You can give the participants varying levels of access rights to requests. For details, see Configuring Participants for Requests.

  • Notifications. Use this tab to configure emails to be sent if specific fields in the request type are completed. For details, see Configuring Notifications for Request Types.

  • User Data. This tab displays information captured by user data fields, which are custom fields that you create to capture specific information that is not captured by standard PPM fields. If no user data fields are defined for the request type, the User Data tab is disabled. For detailed information on user data and how to create user data fields, see Configuring User Data.

  • Ownership. Use this tab to specify who can edit the request type configuration. For details, see Configuring Ownerships of Request Types.

  • Resources. Use this tab to:

    • Enable tracking of actuals in Time Management.

      Note: Actual values, or actuals, represent the amount of time (in hours) that a resource has worked on an activity or request, the amount of time that is estimated to remain, and the percent of work that is completed.

    • Enable tracking of resources assigned to requests of this type.

    • If resource tracking is enabled, configure resource security on the request type. (Determine who can access and modify the resources and actuals displayed in the Resource section of the request details page in the PPM Dashboard.)

    For details on how to use the Resources tab, see Configuring Resource Tracking, Tracking Resources Assigned to Requests, and Configuring Request Types for Use with Time Management.

  • Help Content. Use this tab to add help content to fields, sections and request types. For details, see Configuring Help Contents for Request Types .