...
Notification setup described in this section is with respect to project level requests (build, deploy, test, utility etc.). Requests can be either manually triggered or automatically including pipeline execution.
Event Name | Attribute Name on User Settings | Default Recipients | Description |
|---|---|---|---|
Request Approval Pending | Notify on Approval Required |
| Submitted request has pending approval. |
Request Scheduled | Notify on Request Scheduled |
| Submitted request is scheduled for execution. |
Request Approval Rejected | Notify on Request Rejected |
| Approver has rejected pending approval. |
Request Deploying | Notify on Request Deploying |
| Request is ready for deployment, i.e. all approval and schedule requirements are met or were not present. |
Request Completed | Notify on Request Completed |
| Request is successfully executed. |
Request Failed | Notify on Request Failed |
| Request failed during execution. |
1 - Submitter is a user that initiates build, deployment, utility or test request. Submitter recipient notifications can be turned off if desired for specific user by controlling specific attribute on User Settings. If request is initiated from pipeline, there will be no submitter notification.
...
Select a Type and Recipient.
Type | Recipient |
|---|---|
<Any valid email address> | |
Group | <Any valid FlexDeploy group> |
User | <Any valid FlexDeploy user> |
Click the Save button when finished.
...