As with business rule categories, business rule priorities help you manage and track 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 trace rule use. Priority metadata allows rules to be searched using the Business Rule Search Engine, with the option of sorting results by priority.
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 assigned 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 added to the repository and associated with business rules, you can run a search to see rules associated with a specific priority within a repository.
Guidelines
- When you add a priority, you give it a unique ID value, a name, and, optionally, a description.
- 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 inherited/derived (child) rule, the change is propagated to the child rule. Conversely, you can edit a derived (child) rule, overriding the priority set in the library (parent) rule, and propagating the changes to the parent.