Email is used as alerting notification mechanism for project execution events. If you are not interested in receiving emails for specific events, you can unsubscribe from User Settings page.A notification is a mechanism for alerting people of events within the FlexDeploy application. Alerting mechanism is email. Any Email communication settings must be completed for notifications to work. Notification for project execution events are processed even when request is initiated automatically using release and pipelines.
There are some default recipients for each event (see table below), but any person with an email address can subscribe to specific events and receive notifications, whether they are . This possible even when recipient is not a configured user within FlexDeploy or not. See section below for configuring additional notifications beyond default recipients. Unlike approvals & windows, notifications are additive (on Project Explorer hierarchy) and any notification that is found will be evaluatedprocesses. This is accomplished by searching up the project navigation tree from the deploying application or project until the root folder is reached.
...
| Event Name | Attribute Name on User Settings1 | Default Recipients2 | 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 - User will receive notifications when he/she is the submitter of a Submitter is a user that initiates build, deployment, utility or test request. These Submitter recipient notifications can be turned off if desired for specific user by controlling specific attribute on User Settings.
2 - Commit users are derived from change logs captured during build, which are considered for notification when that specific build (project version) is deployed.
Create Notifications
| Include Page | ||||
|---|---|---|---|---|
|
...