Table of Contents

Locking the release


Only available versions of this content are shown in the dropdown

After all merges are completed, the release engineer locks the applications and rulesets to be released. They are also responsible for creating the new, higher-level ruleset versions and higher-level application rules for the next release.

To lock the release, do the following steps:

  1. In Dev Studio, click Application Structure Ruleset Stack .

  2. Click Lock & Roll.

    As a best practice, lock your built-on applications first, and then work your way up the stack to your top-level application. This way, as each higher version application rule is created, you can open that rule and update the version of the built-on application.
  3. For each ruleset:

    1. Click Lock and provide a password.

    2. Click Roll.

  4. Click Create a new version of my Application.

  5. Click Run.

The application rules and ruleset versions for the current release are locked and require passwords to make changes. Also, you will have created the higher-level ruleset versions and application rules that will be used for the next release.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.