Version Differences for Notifications

(Prerequisites for Configuring Notifications)
Line 32:
  Note: The "Description" field is populated from the "Description" field when requesting the process. Versions earlier than 4.7.2 seemed to have issues populating this field in the email.    Note: The "Description" field is populated from the "Description" field when requesting the process. Versions earlier than 4.7.2 seemed to have issues populating this field in the email. 
       
- ==Approval Process==   + ==Approval Processes==  
  An approval process can be configured on an environment to require a specified user to log in and grant or reject an approval before a process/deployment can execute. This can be used to ensure that the process being executed is configured correctly, and/or as an added layer of security, ensuring that only the appropriate users are requesting the deployment. This will also send a notification to the users in the approval role configured on the layer of the tool. The following are the steps to configure approvals and assume you have already configured the role doing the approval:    An approval process can be configured on an environment to require a specified user to log in and grant or reject an approval before a process/deployment can execute. This can be used to ensure that the process being executed is configured correctly, and/or as an added layer of security, ensuring that only the appropriate users are requesting the deployment. This will also send a notification to the users in the approval role configured on the layer of the tool. The following are the steps to configure approvals and assume you have already configured the role doing the approval: