Version Differences for Notifications

(Event Notifications)
(Approval Processes)
Line 41:
  #Drag the approval steps onto the field, creating an approval process. The available step under each expandable menu correspond to roles configured on the tool level. This works similarly to editing a component or application process.    #Drag the approval steps onto the field, creating an approval process. The available step under each expandable menu correspond to roles configured on the tool level. This works similarly to editing a component or application process. 
  #Connect the steps from start to finish in the order that you want them to execute and save. This can be executed in parallel or series, or a mixture of both.    #Connect the steps from start to finish in the order that you want them to execute and save. This can be executed in parallel or series, or a mixture of both. 
    + <br>  
- 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. This only sends a notification that an approval is pending. If you need notifications that the approval was granted or rejected, see Event Notifications above.   + *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. This only sends a notification that an approval is pending. If you need notifications that the approval was granted or rejected, see Event Notifications above.  
       
  ==Manual Tasks==    ==Manual Tasks==