Skip to main content

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

Using the RuleSet Stack Landing Page Lock and Roll features for managing ruleset versions

Updated on April 8, 2022

The RuleSet Stack landing page simplifies following the best practices of ruleset locking and application versioning. The landing page provides a summary of the locking status of the ruleset versions in your application, as well as the Lock and Roll button.

Best practices for ruleset versioning include:

  • When possible, all versions in a ruleset should remain locked. Use branch development instead of updating unlocked rulesets directly.
  • Cases where unlocked rulesets may be required:
    • Reports
    • Delegated rules
    • System configurations stored in rules
  • If a ruleset requires unlocked versions, then only the highest version of a ruleset should be unlocked.
  • Once locked, a ruleset version should not later be unlocked.

  1. In Dev Studio clickConfigureApplication Structure RuleSet Stack.
  2. Observe the icons in the Current Application section.
    • If a column contains an unlocked warning icon, then a version lower than the highest is unlocked. You will be able to use the Lock and Roll function on this lower ruleset version to lock, but not to roll (increment). Click the unlock warning icon to view a list detailing the currently unlocked versions. Once the lower versions are locked, you can again use the roll portion of the Lock and Roll function on the highest ruleset version.
    • If the column contains a warning icon, then the ruleset version does not exist, but is included in your application. Check your application to determine if the version of the ruleset was incorrectly entered, or if the ruleset was incorrectly entered. Once this error is corrected, then you can run the Lock and Roll function on this ruleset version, if needed.
  3. Click the Lock and Roll button.
  4. In the Application Lock and Roll window, in the Lock column, select the check box next to the rulesets that you want to lock. If a ruleset is currently locked, has a lower unlocked version, or does not exist, the corresponding icon will appear instead of a check box.
  5. In each unlocked ruleset that you selected for locking, a text box appears under the Password column. Enter a password for the ruleset version.
    Note: The password that you enter appears in plain text to ensure that the password is entered correctly.
  6. In the Roll column, check the box next to the rulesets which are to be rolled to a higher version. If the ruleset is not locked or selected to be locked, the check box for this ruleset will not be available.
  7. Observe the value in the Roll to Version column. By default, the value in this column will be the next highest patch version from the current ruleset. If you are rolling a selected ruleset is to a higher minor or major version, change this value to the appropriate version number.
  8. Select the Application update option from the list below the rulesets appropriate for the environment in which your development is taking place. For more information on these options, see Application Structure landing page.
  9. Click Run.

    You might need to log out and back in to the application before the new version of any incremented rulesets become visible.

  • Previous topic Understanding best practices for version control in the DevOps pipeline
  • Next topic Migrating application changes

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