|
Use the RuleSet Maintenance wizard to move RuleSets, and copy or move RuleSet versions, into a target RuleSet or RuleSet Version. Copying creates the target rules and leaves the source rules unchanged. Moving creates the target rules and then deletes the source rules.
When you move a RuleSet, you select an existing RuleSet and specify a Target name and, optionally, a version. The wizard processes the source rules in each RuleSet Version in the RuleSet and any non-versioned rules associated with the RuleSet. The RuleSet and RuleSet Version fields of each rule are updated to the values specified as the target. The result is that the rule appears to have been deleted from its’ source RuleSet and copied into the target RuleSet. The value of the rules' pzInsKey does not change.
The handling of multiple RuleSet Versions in the RuleSet depends on whether you specify a target version:
For example, if you move a RuleSet containing rules with RuleSet versions 01-01-01, 01-01-02 and 01-01-03 into a new target RuleSet and specify a version of 01-02-01, the target RuleSet version will contain the highest version of all the source rules contained in versions 01-01-01, 01-01-02 and 01-01-03 with lower-versioned duplicates dropped. In this example, if a rule is duplicated in both 01-01-01 and 01-01-02, the rule will be moved from 01-01-02 to the new RuleSet name with RuleSet Version 01-02-01, and the duplicate rule in 01-01-01 will be dropped.
When you move a RuleSet, any of the following non-versioned rules associated with the RuleSet are also moved:
You cannot copy a RuleSet.
Copying a RuleSet Version performs the same function as the Save
As
toolbar
icon. The original source RuleSet Version still exists,
unchanged. Each target rule that is created is identical to the original
source rule with the following exceptions:
You can merge multiple source RuleSet Versions, belonging to the same or different RuleSets by copying or moving them into a single target RuleSet version. For example, you can "skim" the RuleSet by collecting only the highest version of every rule in the RuleSet Versions into the target, or you can compress the RuleSets down to a lower level (01-01-01) or another designated level. You control the merge by specifying the target version and the order in which the RuleSet versions will be processed.
When you select the RuleSet Versions, you establish the order of precedence by the order in which you list them in the wizard interface. The wizard processes the rules in the order listed, top-to-bottom, collects the first version of every rule it finds, and drops other duplicate rules:
For both move and copy operations, you can specify how to handle conflicts if the same rules are found in both the source and the target. You can choose to overwrite the target rules with the source rules, or to not move or copy the source rules that conflict, leaving the target rules unchanged. If you choose not to overwrite the rules, the Summary page of the wizard lists the rules in the source that were skipped because they were in conflict with the target.
The wizard does not change rules that belong to locked RuleSet versions. If a RuleSet version that will be changed by the wizard operation is locked, you are prompted for the password to unlock the Version before proceeding. For example, to copy a RuleSet Version the target rules cannot be locked. The source rules can be locked, since they are not changed by the copy operation. To move a RuleSet or RuleSet Version, both the source and target rules must be unlocked.
As a best practice, make sure that all rules are checked in before you move or copy a RuleSet or RuleSet Version. Select View > Rules > All Checkouts to list all rules checked out.
If the wizard encounters rules to be modified that are checked out, it displays a warning page and provides a report of the checked-out rules. From the report window you can open the rules and check in the ones for which you have permission, or save a list of the rules in a spreadsheet.
You must check in any rules you have checked out or arrange for any rules in the report that are checked out by other users to be checked in before you can complete the wizard. If you exit the wizard to arrange for rules to be checked in, you must restart the wizard from the beginning.
Prerequisites and Preparations
This wizard does not modify references to RuleSets that are deleted or modified. Repair any references to rules that have been moved by the wizard by replacing references to the source RuleSet with the target or another RuleSet. In particular,
- Application RuleSets section on the General tab
- Component and Shared RuleSets section on the General tab
- Production RuleSets section on the General tab
- Override RuleSets section on the Advanced tab
Before merging the RuleSets, the tool creates a backup of each rule named Bkup_SourceRuleSet.zip and Bkup_TargetRuleSet.zip. If needed, you can use the Import ZIP facilities to recover the original RuleSets.
Each execution of this wizard creates an instance of the Log-Merge-RuleSet class, including error messages or other results. The key to this instance is the date and time the wizard was started.
Class rules
do not have a version. Do not delete Class rules (or other
rules that have no version) if any version of the RuleSet remains in use.
In some organizations, audit or compliance policies
may prohibit deleting old rules, even if they are not in use.
About the RuleSet Maintenance wizard 
Tools, accelerators, and
wizards