This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
As we have complex events with partly sensitive information in deeper child objects, we'd like to just store a single event per "change" in the Event Streams and define multiple options for the topic defining a redaction control to remove several child objects of the JSON. E.g. when we have a JSON {state: { publicData: {...}, customer: {}, lock: {}, ...}} we would like to define a redaction that deletes $.state.customer and $.state.lock. In reality the hierarchy is deeper and we might have to delete 10 different paths. Therefore, please support deleting a list of paths.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Note that we also would like to support release version compatibility (stable event structure when e.g. new or changed attributes are defined) by using options. Therefore, redaction should also support renaming of JSON attributes as well as attribute transformation (e.g. transform values 1,2,3,4 to enum literals option_a, option_b, option_c, option_d).