Prevent Rules Migration from Including Script Components
We use multiple script components in our rules, especially to hold common variables for groovy rules. We have noticed that when we promote a rule using migration, any script component used in the rule is also included invisibly. The script components are not shown in the snapshot but importing the rules updates the script components.
The issue is that we have multiple development items going at any time, and we have tight change controls on the rules and scripts. We want to only promote the script components when we choose. Yesterday, we had rule validation failures at promotion because of variables that had not yet been promoted to production but were in our development script components.