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).
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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thanks Sampson, for customer to invoke the publish_all api for Shipnode we have more than a million items for DC warehouse and we would like to trigger only for a specific items/shipnode combination that could send same payload to webhooks or COS. this is what i was looking for as capability.
This functionality already exists, customer can invoke the publish_all api for Shipnode snapshot to get the latest availability information at each node without needing to change quantity.
Recommendation is that Customer should proactively download their failed events on a daily basis if any. When an event fails to propagate to customer webhook or COS (very unlikely), IBM attempts to retry up to 5 times, thereafter the events will be placed in a failed repository to allow consumer to reprocess the data after they download the package. Please see the details on how to retrieve the failed events. This is the recommended path in comparison to invoke a republish blindly.
Information on ProductAvailabilityToSell.ShipNodeSnapshot