Creating and submitting a request for release

When you create a request for release through the Process Requests application, you specify information about the requested release that enables a Release Owner to evaluate whether it will be accepted or rejected. To create a release request, you must have the appropriate permissions to create and submit a process request.

About this task

To create and submit an RFC, complete the following steps:

Procedure

  1. Open the Process Requests application (Go To > Release > Process Requests).
  2. Click Create new to create a new process request.

    The fields in the User Information section are populated with your user information, if that data is available.

  3. In the Process Request Details section, complete the following steps:
    1. Type a description of the request in the Description field; you can add a long description if needed.
    2. Enter a value in the Priority field to indicate the priority of the release, with 1 indicating the highest priority and 4 the lowest priority.
    3. In the Process Manager Type field, select Release.
    4. In the Site field, select the site.
    5. In the Requested Completion field, click the calendar, specify the date you want the request completed, and click OK. The requested completion date is displayed in your time zone; when the request is viewed by a user in a different time zone, the date is shown in the time zone of that user.
    6. Specify a customer in the Customer field if you are creating this request on behalf of a customer. Use the following guidelines to specify a customer:
      • You can select the customer in the Customer field. No CI, asset, or location values are brought in when you select a customer, because customers have multiple CIs, assets, and locations.
      • Rather than selecting the customer in the Customer field, you can specify a CI that is associated with a customer. If you do so, the Customer field is populated with that customer.
      • You can also specify an asset that is primarily associated with a customer. Doing so brings in the customer if no customer-specific CI has been specified.
      • Similarly, if no customer-specific CI or asset is specified, you can specify a location; the primary customer for that location is brought into the Customer field.
      • The system looks first at the CI, second at the asset, and third at the location before bringing in a customer.
  4. In the Request Classification Details section, select Classify in the Classification field, and select a classification that describes the overall purpose of the release that you are requesting.

    After you specify a classification, any extended classification attributes are displayed in the Classification Attributes section, where you can supply attribute values. Classification attributes help you capture information that is necessary for efficiently processing a release. For example, the CIAPPSOFTWARE classification brings in the APPSOFTWARECIPKG attribute; you can expand this attribute and select a CI to populate the Table Value field. The selected CI will be deployed for the release.

  5. In the Target CIs section, click Select > CIs > Select Value, select the CIs that will be targets of the requested release, and click OK.
  6. Click Save to save the request.
  7. Click Submit requestto submit the request.

What to do next

Note: When you submit the request, the Process Requests application starts the submit master work flow. If there are any user prompts or messages shown, click the Route Workflow icon (Route workflow) to complete the workflow interaction.

After you submit the request, correct any errors that are displayed by the submit workflow. If necessary, resubmit the request.

After you successfully submit the request, its Process State is SUBMITTED. The request is displayed in the start center of a Release Owner who is responsible for evaluating release requests and accepting or rejecting them. You are notified when your request is accepted or rejected.



Feedback