Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Jul 21, 2025

Enhance the supplyChange.v2 event schema to allow propagation of custom attributes included in the original IV request.

Problem Statement:
We are using the supplyChange.v2 event to publish IV resonance data to a configured webhook endpoint. As part of our implementation, we are including several custom attributes (e.g., SourceSystemID, AdjustmentReasonCodeID, etc.) in the original Inventory Visibility (IV) request payload.
However, we have observed that these custom attributes are not being returned in the event payload published to the webhook. Upon further investigation and reference to the sample JSON schema of the published supplyChange.v2 event, we confirmed that custom attributes are currently not supported in the event structure.

Expectation:
We request support to:

Enhance the supplyChange.v2 event schema to allow propagation of custom attributes included in the original IV request. Ensure these custom attributes are returned as part of the webhook payload in a defined and consistent structure (e.g., under a customAttributes node).

Provide updated documentation or schema references for implementing this capability.

  • Admin
    Sampson Wong
    Jul 28, 2025

    Supply attribute currently supports supply audit only.

    For exposure in events, this will need to be consider for future enhancement.