You can associate a ruleset with instances of certain data classes, such as organizations and workbaskets. The ruleset associated with an instance of a data class is that instance's associated ruleset.
By definition, a ruleset corresponds to a collection of rules, and does not include data instances. However, to assist in application packaging and migration, you can record an association between a ruleset and data instances. Such associations make it easier to identify which data instances to include in an application package. For such data classes, the two standard properties pyRuleSet and pyIsTagged hold the information.
As you create data instances of certain classes, they are automatically associated with the ruleset that the current application is defined in (the ruleset that the application rule belongs to). This automatic association is controlled by the @baseclass.pyTaggedDataInstances decision table.
Wizards and accelerators that create data instances also automatically associate those data instances with the ruleset for the current application. You can clear the Associated RuleSet field (so the data instance is not associated with any ruleset ) or enter a different ruleset .
Associating a ruleset with a data instance does not affect or restrict any run time behavior. The data instance remains available to all applications regardless of the rulesets that make up the application. If the data instance was imported from another system, it may reference a ruleset that doesn't exist on the current system.