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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Sep 28, 2021

Make sourceTs and updatedTs fields visible in Get Supply and Get Demand API Responses

As an integration consultant, I need to be able to see when the supply and demand for an item was last updated so I can confirm whether or not information is flowing from external systems to IV.

  • The sourceTs and updatedTs will help when performance testing in pre-prod environments enabling us to see when the message was received by IV. We can then compare that to the timestamp the event was sent from the external system to try and identify any latency.

  • The sourceTs and updatedTs will also help when trying to determine if a message made it to IV - especially if we have multiple tests occurring at once and the quantity might not change between multiple Syncs.

  • Example: sync supply for 100 at 12:00, then adjust supply -50 at 12:03, then adjust supply for 50 at 12:10pm... if we run a get supply we will see the quantity of 100 but we do not know if that is from the 12pm sync supply message (and the 2nd and 3rd messages were ignored or lost) or the 12:10 message after the adjustments were done .

  • When testing IV proof of concepts, it will help us determine if message was accepted/ignored when running adjust supply API and sync supply API.

  • It will also allow us to know what the last synced sourceTs was so we can increment the timestamp when sending the sourceTs in the request body rather than having to calculate it each time.

What is your industry? Computer Services
How will this idea be used?

As an integration consultant, I need to be able to tell