Show me this set of test questions.

  1. They have the same Conditions but different Actions.
  2. All combinations of possible values from the Conditions' values sets are covered in rules on the Rulesheet.
  3. No, not all ambiguous rules are wrong or need to be resolved before deployment. Ambiguities can exist in Rulesheets when there are rules that are completely unrelated to each other. In those cases, it may be appropriate for both rules to fire if the Conditions for both are met.
  4. No, not all instances of incompleteness are wrong or need to be resolved before deployment. Incomplete Rulesheets may be missing combinations of Conditions that cannot or should not occur in real data. In those cases, rules for such combinations may not make sense at all.
  5. Conflict Checker: second icon; Compression Tool: fifth icon; Expansion Tool: first icon; Collapse Tool: third icon; Conflict Filter: sixth icon.
  6. An ambiguity can be resolved by making the Actions match for both rules, or by setting an override for one of the rules.
  7. False. Defining an override does not specify an execution sequence, but rather specifies that the rule with the override always fires instead of the rule being overridden when the Conditions they share are satisfied.
  8. False. The Completeness Checker auto-completes the Condition's value set prior to inserting missing rules. This ensures that the Rulesheet, post-application of the Completeness Check, is truly complete.
  9. The Completeness Checker detects Rulesheet incompleteness caused by an incomplete values set because it automatically completes the value set before inserting missing columns.
  10. Yes. One rule can override multiple other rules by holding the CTRL key to multi-select overrides from the drop-down.
  11. No, overrides are not transitive and must be specified directly between all applicable rules.
  12. No, rules created by the Completeness Checker may be made up of combinations of Conditions that cannot or should not occur in real data. In those cases, rules for such combinations may not make sense at all.
  13. A dash specifies that the Condition should be ignored for this rule.
  14. False. The Expansion Tool merely expands a Rulesheet so that all subrules are visible. The results can be reversed by using the Collapse Tool.
  15. True. It may be reversible using Undo, or by manually removing redundant subrules after expansion.
  16. 64 (4 x 4 x 4)
  17. It is not necessary to assign actions for a rule column if that combination of conditions cannot or should not exist in real data. It is a good practice to disable columns added by the Completeness Check that you determine need no Actions.
  18. They can be disabled, deleted, or left as-is with no Actions (but being left as-is is not recommended because it will cause activity that can impact performance).
  19. Compression Tool
  20. The compression performed by the Completeness Checker is designed to reduce a large set of missing rules into the smallest set of non-overlapping columns, while the compression performed by the Compression Tool is designed to reduce the number of rules into the smallest set of general rules (i.e. create columns with the most dashes).
  21. Even very large databases may not contain all possible combinations of data necessary to verify Rulesheet completeness. In short, the databases may be incomplete themselves.
  22. Renumber the rules and potentially ask you to consolidate Rule Statements if duplicate row numbers result from the renumbering.
  23. Subsumation occurs when the Compression Tool detects that a more general rule expression includes the logic of a more specific rule expression. In this case, the more specific rule can be removed.