We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Rules should pick up metadata assigned to data classes
Currently, Rules within WKC only picks up data classes, business terms, and classifications that are applied directly to columns/assets within the Catalog, under the asset preview section. We expected that we would be able to create dependent data classes that would inherit attributes (like tags, classifications, and business terms) from parent data classes-- and after applying a Rule to a parent data class only, we expected to have the Rule also affect the dependent data classes.
For example, if we were to
1) list data classes 'First Name' and 'Last Name' as dependent data classes under the 'Person Name' parent data class (in the Governance>Data Classes section of WKC),
2) add a custom classification or tag to the 'Person Name' data class (e.g. 'PII/PHI-Redact' classification), and
3) create a redaction Rule (in Governance>Rules) with criteria that applies to that specific classification or tag and/or includes only the parent data class 'Person Name'-- we would expect to see that the dependent data classes 'First Name' and 'Last Name' inherit the classification or tag from the parent data class 'Person Name' and (even though the dependent data classes are not explicitly included in the Rule) that the dependent data classes are also redacted.
This functionality would offer our team more flexibility for Rule creation and masking and allow us to group dependent data classes under custom-created parent data classes with custom classifications/tags.
Do not place IBM confidential, company confidential, or personal information into any field.