Managing Release Control Notifications

Notifications help keep release management stakeholders informed of release status information. If subscribed, e-mail notifications are sent to Serena Release Control users to alert them of actions requiring their attention and to provide important release status information.

Serena Release Control 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 Control are shown in the following table.

Entity

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

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

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

Other (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

Development Change Request (DCR): SBM Incident

I - Any Incident changes owner

I - Any Incident changes state

I - Any Incident changes to inactive

I- Any Incident I submitted changed state

I - Any Incident I submitted changed to inactive

I- Any Incident is submitted

I - I become the owner of any Incident

Business Change Request (BCR): SBM Issue

I - Any Issue changes owner

I - Any Issue changes state

I - Any Issue changes to inactive

I- Any Issue I submitted changed state

I - Any Issue I submitted changed to inactive

I- Any Issue is submitted

I - I become the owner of any Issue

Development Change Request (DCR): Dimensions CM Request

RV - Any Change Request changes owner

RV - Any Change Request changes state

RV - Any Change Request changes to inactive

RV - Any Change Request I submitted changed state

RV - Any Change Request I submitted changed to inactive

RV - Any Change Request is submitted

RV - I become the owner of any Change Request

Request for Change (RFC): SSM CAR

CAR - Any Change Request changes owner

CAR - Any Change Request changes state

CAR - Any Change Request changes to inactive

CAR - Any Change Request I submitted changed state

CAR - Any Change Request I submitted changed to inactive

CAR - Any Change Request is submitted

CAR - I become the owner of any Change Request

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

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:

What is the Impact?

If you add a notification, you must subscribe users to it so that they will be sent to them upon the event associated with the notification.

How Do You Change It?

You can manage notifications in SBM System Administrator according to the SBM documentation.

Documentation References

Complete documentation on configuring SBM notifications is in the Serena Business Manager System Administrator Guide in "Managing Notifications".