Validation requests
| Required Roles | Environment Release Operator and/or Manager Release Project Manager Application Database Administrator |
| Required Rights (by category) |
Validation Requests |
| Perspective |
Operational Console Management |
| Access |
 DROPS Server →  Deployment Process →  Validation Requests DROPS Server →  Deployment Plans → Validation Requests |
If a deployment plan or a deployment process, or any entity included in one, requires validation before it is allowed to move forward, a validation request notification is sent to the user(s) in the designated role(s).
Validation requests are generated during the deployment process if the Validation parameter is activated. They are activated at the highest process-level of the deployment process diagram and at the activity-level. They can be executed before any processes can begin or after they're completed. Required requests must be attended to before deployment can continue and the validator may also be required to provide a reason for either accepting or rejecting the request.
To view and approve/reject validation requests, a user must have the Release Operator role for the environment in question.
For more information about defining when validation requests are generated, refer to Editing deployment process properties.and Editing deployment plan properties.
The Validation Requests view displays all of the pending requests that you must reply to in order for the associated deployment plan or deployment process to continue forward.
When a user, different than the one that started the execution of deployment plan, gets involved in the validation process, this user becomes the new executor of all the following deployment plan instances.
Responding to requests
The validation notification email is sent to the users who have the correct role to respond to validation requests.
For more information about editing the default content of automatic emails and defining the mail configuration, refer to
There are two ways to respond to a pending validation request:
- Fill in the validation request manually,
- Validate immediately.
Fill out the validation request editor
To fill out the validation request manually, select the request in the Validation Requests view and either click the 
respond icon or right-click on it and select Respond to open the Validation Request editor.
To validate or reject the request to carry out the corresponding step, activity, action, stage etc. select the response from the Response drop-down list.
- A Rejected request will stop the action and the process or plan will not continue forward.
- An Approved request will execute the action and enable the process or plan to continue.
Enter details about the decision made in the Comment field. This step may be required to save the approved or rejected request if the user who created it ticked the Validation Reason is Mandatory checkbox.
To save changes made, click the Save button.
You can only respond to a validation request once. After the selected option is saved, the Response field is read-only.
Validate immediately
To validate a request immediately from the Validation Requests view, select it and either click the 
validate icon or right-click on it and select Validate immediately.
Click OK.
If the Validation Reason is Mandatory checkbox is ticked in the original request, enter details about the decision made in the dialog.
Result The request is approved and the process or plan is allowed to continue.
Reviewing processed requests
To view all of the processed validation requests, select the 
Processed validation requests node from Validation Requests in the Console Explorer.
The Validation Requests view displays all of the requests that you have replied to. Double-click on a request to open the Validation Request editor.
