Business Rule Priorities - trillium_discovery - Latest

Trillium Discovery Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
Latest
Language
English
Product name
Trillium Discovery
Title
Trillium Discovery Center
Copyright
2024
First publish date
2008
Last updated
2024-10-18
Published on
2024-10-18T14:55:05.094442

As with business rule categories, business rule priorities help you manage business rules throughout the data quality life cycle. Every business rule in your repository is associated with a priority. This helps you manage, organize, and track rule use.

There are ten priorities available out-of-the-box. Use these default priorities as templates to help build your collection of priorities as you add more business rules to your repositories.

Working with Priorities

When you add a priority, you give it a unique numeric ID. This ID has no inherent value: you decide how to weigh it depending on its impact and importance. In this way you create a business rule hierarchy where each rule carries a level of importance depending on the priority you assign it.

For example, say you have ten priorities. You could use 1-5 for higher priority rules, with 1 the highest/most important. Then use 6 through 10 for rules that have a lower degree of priority. As your business standards change, modify rule priorities to reflect these changes.

After priorities are associated with business rules, you can run a search to see rules associated with a specific priority within a repository.

Guidelines

  • The Discovery Center includes ten priorities available out-of-the-box.
  • When you add a priority, you give it a unique ID value, a name, and, optionally, a description.
  • Priorities can be edited, associated to business rules, and deleted.
  • When you create a business rule, the lowest numeric priority available in the repository (for example, Priority 1) is automatically associated with the rule unless you select another priority.
  • When importing a rule into the Library, note the following behavior:
    • If the rule was created in an earlier version of Trillium, the lowest available priority will be associated to the rule by default.
    • If the rule contains a priority that does not exist in your repository, the priority will be added.
    • If the rule contains a priority that already exists but the names and descriptions vary, the names and descriptions of the priority in the current repository will be used.
  • If you modify a priority on a library (parent) rule associated with an data source (child) rule, the change is propagated to the child rule. Conversely, you can edit a data source (child) rule, overriding the priority set in the library (parent) rule, and propagating the changes to the parent.