Skip to main content

Auto Create Relationship for Rule associated with Concept or BP

Syniti Knowledge PlatformCatalog

On a rule you can associate Business Processes and Concepts, however without a relationship, those rules aren't visible from the Business Process or Term. Assigning those pieces to a rule should auto create the relationship.

Posted by Alyssa Sliney ·
Status: Unlikely to Implement1 comment

Log in to comment and vote

Comments1

  • John Munkberg

    Team•

    Mar 7

    As we continue to work to improve the Data Catalog - rules will become children of the Dataset - because that is where the data is.

    In most cases - a rule is associated with a specific data element. Some rules reference multiple data elements and therefore can be registered at the Dataset level. Some rules are associated with the Record Type (Material Type, Customer Type, etc). And rarely, a rule may span across Datasets and therefore we support registering Rules at the Subject Area level.

    Finally, some rules are specific to the TYPE of Data Element. Rules such as ‘all emails must have a domain and an ‘@’ symbol are not specific to a single data element, but the TYPE of data element across all Datasets. These Data Element Type rules would have many enforcements across any dataset that contains and Email address.

    Generally - Rules don’t belong to a Business Process. The Business Process references data via the associated Datasets. Therefore the quality of the business process is based on the quality of the Data that drives that business process. If a specific Business Process includes a step to “Check Inventory Availability”, then having poor inventory quality would degrade the entire business process. Having bad inventory data probably affects dozens of Business Processes…

    Directly associating rules with a Business Process is not sustainable as any user who defines a new Rule would have to comb through dozens of Business Processes to add/remove Rules as the business evolves.

    Of course - we will continue to evolve our catalog and refine our DQ logic, so the above is open to review and subject to change as we continue development.