Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Use a production RuleSet with unlocked version for frequently changed rules

Updated on September 13, 2021


A developer asks:

I have a SmartAdjust application where we want to change WriteOff levels, Cutoff times, and other rules on the fly in production, even though the rest of RuleSets are locked down. 

We don't want to migrate in RuleSet versions to get changed values for those sorts of rules.  Is there a best practice approach to accomplishing this?


Place such rules in a production RuleSet — a RuleSet and version which doesn't get moved in from anywhere else, but instead just resides in the production system.   Leave the top version of that RuleSet unlocked, and if those rules are truly dynamic, you can decide to not require checkout of those rules.

For each rule in the production RuleSet, provide a baseline or default functionality in another (non-production-residing) RuleSet, so that your QA and development environments have a desired behavior.


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