Promoting Serena Release Manager

After you import a solution, you promote the associated snapshots into your environment. Promoting the snapshots places the contents of the solution, including all reports, notifications, process apps, and auxiliary table data, onto your SBM Server.

Important: You must promote the snapshots before you modify and deploy them. Promoting maintains data that is necessary for some operations such as maintaining internal IDs. Deploying first could cause compatibility problems later on.

Note the following information about promoting the snapshots:

Important: You must promote the RLM – Release Train snapshot before you promote the RLM – Approvals snapshot.
This ensures that reports in the Approvals process app have access to fields from the Release Train process app. If you did not promote the process apps in this order (and users see a SQL error in the Release Dashboard), promote the Approvals snapshot again.
It is recommended that you promote all of the snapshots; however the sample apps are optional.
Tip: If you do not plan to use a particular process app, it is recommended that you still promote the snapshot (you do not need to make it available to your users). Each process app references other process apps and you will encounter reference errors in SBM Composer when you attempt to modify the process apps if you do not promote them all.
If you encounter any problems with promoting the snapshots, refer to Troubleshooting Promotions.