IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting 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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 offering manager 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 notifications 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.

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.

  • Guest
  • Sep 28 2021
  • Under review
What is your industry? Computer Services
How will this idea be used?

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

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.