Question

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?

Response

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.