RLC: After upgrading to version 6.2, existing release trains are locked by default

ID:    S142133
Published:    15 May 2017
Updated:    13 June 2017

Operating System(s)

  • All Windows


  • Release Control 6.2


After upgrading to Release Control version 6.2, Train is Locked field is set to Yes or null for existing release trains, but set to No for new release trains. The result is that all existing release trains are locked.

It is recommended that you set this to No for all trains through mass update, then go back and manually set any to Yes as needed.


Enable Mass Update in the Release Package Project

Mass update may be disabled for these fields, so if you want to mass update these fields on your release packages, an administrator should do the following:

  1. In SBM Application Administrator, select Projects > Release Package.

  2. In the content area, select the Release Packages project and click the Details icon.

  3. In the navigation pane, select Default Fields.

  4. Select Allow Mass Update for the fields you want to update.

  5. Save the changes.

Mass Update to Select Values for the Custom Column Fields

Once mass update is enabled for these fields, do the following:

  1. In Work Center in the Release Control application group, a list of your release packages, such as All Packages, click the Apply actions to multiple items icon in the upper right of the list pane. 
  2. Select all of the release packages (or just the ones you want to update).
  3. Click Mass Update.
  4. Select Update from Any and then click Next.
  5. Add the values to the fields you want to set.
  6. Click Finish and then click OK.

Applies To

Release Control 6.2

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs