Every action configured in the Set Extractor or Set Loader is configured as a rule. There are rules which determine where to connect, rules which determine which rows to extract and others which determine how to load the resulting subset data. Some operations, such as disabling a foreign key or truncating a table will require a separate specific rule for each action. This means if every foreign key is to be disabled, or every table in the target schema is to be truncated prior to the load of the subset rows, then there must be a distinct rule for each item operated on.
If such actions were configured as individual rules, then the large quantity of such rules could visually overwhelm the user. For example, there can be thousands of tables in a schema. A display listing an individual load rule for each table would be hard to use and would be cumbersome to configure and maintain. Since all of the actions of any one type are essentially identical, it is much more efficient to collect all of the actions together under one container rule which acts as a manager. The items to be operated on are listed in the manager rule and the manager rule provides the ability to view, configure and manage those actions. There is one rule for each type of operation: disable foreign keys, truncate tables, load tables, enable triggers etc. The manager rule presents a simple easy to handle listing on the display the contents of which can be opened for viewing should the need arise. When executed, the manager rule itself controls the execution of the configured operations. Errors and statistics are handled by the manager rule and presented to the user in a useful summary form and all run operations are noted in the log.