Using CA Service Catalog for Administrators › Discrete Request Life Cycle › Set the Configuration Parameters

Set the Configuration Parameters

To enable the discrete handling of requests pending action, set the related configuration parameters. You can use these configuration parameters individually; however, they are most effective when you use them together to achieve the request processing that you want.

To set the configuration parameters

1. Click Catalog, Configuration, Options, Request Management Configuration.
2. Set the following parameters:

   Allow Discrete Handling of Service Options After

   Specifies the status at which request managers (approvers and fulfillers) can handle requests pending action (approval, rejection, or fulfillment) discretely. When the request reaches the status you specify, request managers can discretely (individually) approve, reject, or fulfill each service option in every service in the request.

   In other words, you can use this parameter to specify that pending actions are assigned at the service option level, rather than the service level.

   The setting you specify applies to the request from the starting status that you specify through the remainder of the request life cycle.

   Valid values are Submitted, Pending Fulfillment, or Completed.

   The default is Pending Fulfillment, for backward compatibility, so that the request life cycle functions the same as it did in past releases before this parameter was implemented.

   See the sample settings and their meanings.

   Allow Discrete Request Life Cycle After

   Specifies the status at which individual service options in a service and individual services in a request advance to further statuses in the request life cycle independently. Here, independently means without requiring or waiting for any other service options in the same service or any other services in the same request to advance to any further statuses.

   As soon as the request reaches the status that you specify, the service options that you approve or fulfill can complete the remainder of the request life cycle, even if other service options in the same service are not acted on.

   Similarly, as soon as the request reaches the status that you specify, the services that you approve or fulfill can complete the remainder request life cycle, even if other services in the same request are rejected or not acted on.

   Valid values are Submitted, Pending Fulfillment, or Completed.

   The default is Completed, for backward compatibility, so that the request life cycle functions the same as it did in past releases of the product before this parameter was implemented.

   The setting you specify applies to the request from the starting status that you specify through the remainder of the request life cycle.

   See the sample settings and their meanings.

   Allow Discrete Handling for Reject

   Specifies the effect of the rejection of a single service or service option upon other services and service options in the same request:

   • If this setting is Yes, when you reject a service or service option, the remaining services or service options can advance if they are approved. That is, other services in the same request can advance in the request life cycle if they are approved. Similarly, other service options in the same service can advance in the request life cycle if they are approved.
   • If this setting is No, when you reject a service or service option, the entire request is rejected. That is, all services in the same request are rejected and can no longer advance in the request life cycle, even if they were previously approved. Similarly, all service options in the same service are rejected and can no longer advance in the request life cycle, even if they were previously approved.

   The default is No, for backward compatibility, so that the request life cycle functions the same as it did in past releases of the product before this parameter was implemented.