Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Locking the release

Updated on April 8, 2022

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 ApplicationStructureRuleset Stack.
  2. Click Lock & Roll.
    Note: 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.
Result: 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.
What to do next: Configure higher environments: Staging, BOE, and Production. For more information, see Configuring higher environments.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us