Using CA Service Catalog for Administrators › Discrete Request Life Cycle

Discrete Request Life Cycle

With a discrete life cycle, you can enable services and service options to advance to higher request statuses without waiting for all other services and service options to reach the same statuses. Consequently, services and service options can reach Fulfilled and Completed statuses, and can be invoiced earlier than without a discrete life cycle, even if a request manager rejects one or more services or service options in the same request.

As an administrator, you can optionally specify discrete settings for the request life cycle for individual business units, as follows:

• Depending on the configuration you choose, you can specify the status at which request managers (approvers and fulfillers) can discretely (individually) approve, reject, or fulfill each service option in every service in the request. The setting you specify applies to the request from the starting status that you specify through the remainder of the request life cycle.
• You can optionally specify 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. The setting you specify applies to the request from the starting status that you specify through the remainder of the request life cycle.
• You can optionally specify 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.
  • If this setting is No, when you reject a service or service option, the entire request is rejected, even other services or service options that were previously approved change to Rejected status and can no longer advance in the request life cycle.

To specify these discrete settings, set their configuration parameters.

Note: For all these parameters, the default settings maintain backward compatibility, so the request life cycle functions that same as it did in past releases before this parameter was implemented.