Skip to Main Content
Integration


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Status Future consideration
Created by Guest
Created on Aug 6, 2025

Make existing Option in use still extendable by defining additional redactions so subscribed systems can continue using existing credentials

We have the following EEM situation that seems not yet been addressed in a solid manner by EPM. We use redaction to strip away some confidential attributes from the single source event (complex object). When we publish the option and e.g. 20 systems already subscribed, we might get new attributes in the backend system publishing the source event that find its way into the event. We do not want to produce 2 different event objects per backend change on non-schema breaking changes. However, when the new attribute is also confidential (only few systems may see it and another Option is available for that) it should be removed by redaction as well. This, however, means that we need to change the options, which is not possible today as long as it is published and subscribers are registered. So we have to define a new option with an additional redaction. For our clients this means they need to subscribe for the new option (with the additional redaction) and replace the credentials in their code/config to still receive the same data as before. We also would need to monitor the existing subscriptions to make sure that no system still uses the old option and receives confidential data. We need to be able to extend the redactions of an existing published option (or some alternative approach to avoid having to unsubscribe all existing clients).

Idea priority High