Share this page

# Request Type Checklist

Table 2-6. Request type configuration checklist provides a configuration consideration checklist to help define your Demand Management system. For a complete list of request type considerations, see Request Type Configuration Sheets.

Table 2-6. Request type configuration checklist
Done | Request Type Check Item | Configuration Consideration
--- | --- | ---
| Request type considerations. | A request type must be defined for each type of request to be resolved. This includes creating fields that describe the request and decisions and field logic required to process it during resolution.
| Is a request header type associated with the request type? | A request header type must be associated with the request type. If no appropriate request header type exists, create one.
| Are fields defined? | Fields are required to define the request. Ensure the correct parameters are used to describe the request to be processed. For more information, see Create request type fields and the Commands, Tokens, and Validations Guide and Reference.
| Are request rules defined? | You can set rules to automatically populate fields in the request, or define more dynamic behavior on the request form. For details, see Request type rules.
| Are request status values defined? | Define the status values that the request can have and associate them with the request type. You can add new status values, if necessary. For details, see Configure request statuses for request types .
| Are status dependencies set? | You can configure request fields to be hidden, required, read-only, cleared, or reconfirmed, based on the request status. For details, see Configure request field status dependencies.
| Is request security set? | You can control who participates in request resolution. For information about how to set request security, see Create request type fields and the Security Model Guide and Reference.
| Is request field security set? | You can configure request fields to be invisible to specific users and security groups. For more information, see Create request type fields and the Security Model Guide and Reference.
| Are request notifications set? | You can configure notifications to be sent automatically at specific points in your process. For details, see Configure notifications for request types.
| Are user data fields defined? | Use user data to define global fields for requests, if necessary. For more information, see Configure user data.
| Are fields defined for the request type? | Fields are required to define the request. Make sure that the correct parameters describe the request. For more information, see Create request type fields.
| Is the request type enabled? | Disabled request types cannot be submitted by users. (You can find the Enabled option in the Request Type window.)
| Cover all request type and workflow considerations. | Decide which request type status values correspond to each workflow step. Decide which workflow steps change the request's Assigned To or Assigned Group fields. Decide which workflow steps are to execute any request type commands. Verify that workflow step source validations and request type field validations agree. This is required if a transition is based on a field value (using tokens, SQL or PL/SQL execution types). Allow the request type use for the workflow (set on the workflow window Request Types tab). Allow the workflow to be used by the request type (set on the Request Type window Workflows tab).

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: