Copying ruleset versions in a RuleSet Maintenance wizard
Promote reuse of resources across your application to save time and make your development process more efficient by copying ruleset versions. Instead of creating new elements of your application, you can copy existing rules so that you perform necessary modifications and implement existing functionality for your business requirements.
For example, you can copy a ruleset version that includes service-level agreement rules for an HR department in your organization. You can then modify parts of the rules to apply to the Engineering department.- In the header of Dev Studio, click .
- On the Rulesets tab, in the Refactor Rulesets Utilities list, click Copy/Merge RuleSet.
- In the RueSet Maintenance section, in the list of options, select Copy.
- Specify the type of resources that you want to copy by selecting RuleSet
Versions.You cannot copy an entire ruleset.
- In the Available Source RuleSet(s) list, select ruleset versions
that you want to copy, and then click Move.
- Optional: To specify the order in which the wizard processes ruleset versions, in the
Order of precedence during Copy/Merge list, reorder the ruleset
versions by clicking the Move up and Move
down buttons.If you work with multiple ruleset versions, the wizard processes ruleset versions in the order from top to bottom of the list. As a result, the wizard processes rules from the top of the list first are first and omits duplicate rules in the following versions in the list. Then the wizard processes any remaining rules in the second ruleset version in the list and omits duplicates in the following versions. The wizard then continues to process ruleset versions in the same way until the end of the list.
- In the Target section, in the Target RuleSet
Information column, provide information about the target ruleset:
- In the Name field, enter the name of the target ruleset.
- In the Version field, enter the version of the tagret ruleset.
- In the Target section, specify how you want the wizard to behave
if both source and target rulesets include rules with the same names:
- To overwrite target ruleset instances with the source ruleset instances, select Yes.
- To omit processing of source rules that duplicate existing target rules and leave the target rules unchanged, select No.
For example: The following figure shows a sample configuration for copying ruleset versions: Copying ruleset versions 
- Optional: To copy rulesets with ruleset prerequisites, select the Copy missing Ruleset Prerequisities check box.
- Click Next.
- In the RuleSet Maintenance section, analyze information about source and target rulesets for the copy operation.
- To run the operation in the background, in the Run as a background
process? row, selectYes.Copying ruleset versions as a background process saves time when the source ruleset versions contain a significant number of rules. If you have an email account configured in Pega Platform, you receive an email when the process is complete.
- Click Copy.
- When the copying is complete, in the RuleSet Maintenance section, review the results of the operation.
- Optional: To review a detailed list of copied rules, click Click here to view list of
Processed Rules.
- Optional: To share the list of rulesets with other developers or to review the list offline, in the DisplayRulesProcessed window, click Export Page to Excel, and then close the window.
- Click Done.
Previous topic RuleSet Maintenance wizard Next topic Merging rulesets and ruleset versions in a RuleSet Maintenance wizard