Notifications help keep release management stakeholders informed of release status information. If subscribed, e-mail notifications are sent to Serena Release Manager users to alert them of actions requiring their attention and to provide important release status information.
Serena Release Manager provides a default set of notifications, and you can configure these as needed to support your organization. The notifications configured by default for Serena Release Manager are shown in the following table.
| Workflow | Notifications |
|---|---|
|
Release Train |
RTN - Any Release Train changes owner |
|
RTN - Any Release Train changes state |
|
|
RTN - Any Release Train changes to inactive |
|
|
RTN - Any Release Train I submitted changed state |
|
|
RTN - Any Release Train I submitted changed to inactive |
|
|
RTN - Any Release Train is submitted |
|
|
RTN - I become the owner of any Release Train |
|
|
Application Release |
AR - Any Application Release changes owner |
|
AR - Any Application Release changes state |
|
|
AR - Any Application Release changes to inactive |
|
|
AR - Any Application Release I submitted changed state |
|
|
AR - Any Application Release I submitted changed to inactive |
|
|
AR - Any Application Release is submitted |
|
|
AR - I become the owner of any Application Release |
|
|
Release Package |
RP - Any Release Package changes owner |
|
RP - Any Release Package changes state |
|
|
RP - Any Release Package changes to inactive |
|
|
RP - Any Release Package I submitted changed state |
|
|
RP - Any Release Package I submitted changed to inactive |
|
|
RP - Any Release Package is submitted |
|
|
RP - I become the owner of any Release Package |
|
|
Deployment Task (and sub-workflows) |
D - Any Automation Task fails for Release Engineer or Manager |
|
D - Any Vault Task fails for Release Engineer or Manager |
|
|
D - Any Deployment changes owner |
|
|
D - Any Deployment changes state |
|
|
D - Any Deployment changes to inactive |
|
|
D - Any Deployment I submitted changed state |
|
|
D - Any Deployment I submitted changed to inactive |
|
|
D - Any Deployment is submitted |
|
|
D - I become the owner of an In Progress Automation Task |
|
|
D - I become the owner of an In Progress Manual Task |
|
|
D - I become the owner of an In Progress Vault Task |
|
|
D - I become the owner of any Deployment |
|
|
Release Template (Deployment Process Template) |
RT - Any Release Template changes owner |
|
RT - Any Release Template changes state |
|
|
RT - Any Release Template changes to inactive |
|
|
RT - Any Release Template I submitted changed state |
|
|
RT - Any Release Template I submitted changed to inactive |
|
|
RT - Any Release Template is submitted |
|
|
RT - I become the owner of any Release Template |
|
|
Rlm Aux (Auxiliary) |
RA - Any Rlm Aux changes owner |
|
RA - Any Rlm Aux changes state |
|
|
RA - Any Rlm Aux changes to inactive |
|
|
RA - Any Rlm Aux I submitted changed state |
|
|
RA - Any Rlm Aux I submitted changed to inactive |
|
|
RA - Any Rlm Aux is submitted |
|
|
RA - I become the owner of any Rlm Aux |
|
|
Environment |
E - Any Environment changes owner |
|
E - Any Environment changes state |
|
|
E - Any Environment changes to inactive |
|
|
E - Any Environment I submitted changed state |
|
|
E - Any Environment I submitted changed to inactive |
|
|
E - Any Environment is submitted |
|
|
E - I become the owner of any Environment |
|
|
Vault Request |
VR - Any Vault_Request changes owner |
|
VR - Any Vault_Request changes state |
|
|
VR - Any Vault_Request changes to inactive |
|
|
VR - Any Vault_Request I submitted changed state |
|
|
VR - Any Vault_Request I submitted changed to inactive |
|
|
VR - Any Vault_Request is submitted |
|
|
VR - I become the owner of any Vault_Request |
|
|
Vault Template |
VT - Any Vault_Request changes owner |
|
VT - Any Vault_Request changes state |
|
|
VT - Any Vault_Request changes to inactive |
|
|
VT - Any Vault_Request I submitted changed state |
|
|
VT - Any Vault_Request I submitted changed to inactive |
|
|
VT - Any Vault_Request is submitted |
|
|
VT - I become the owner of any Vault_Request |
What Can You Change in Release Manager?
Notification changes are done in native SBM.
What Can You Change in SBM?
You can modify the provided notifications and configure additional notifications as needed to support your release management processes.
Notifications in SBM are e-mail messages sent to users when certain events or conditions occur in the system. Notifications can also be used to automatically add and remove items from folders and to execute scripts.
You can change the following notification information:
Add notifications
Modify notifications
Subscribe users to notifications
What is the Impact?
If you add a notification, you should subscribe users to it so that the notification is sent to them when the associated event occurs.
How Do You Change It?
You can manage notifications in SBM Application Administrator according to the SBM documentation.
Documentation References
Complete documentation on configuring SBM notifications is in the Serena Business Manager Application Administrator Guide in "Managing Notifications".