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.
Reset dirty Node - Optimized approach for IV
We are looking at an option where we have one invocation to reset the dirty flag instead of doing for each item ship node. In full sync there will be 150K items and 3000 stores hence this approach of resetting dirty node for each item and ship node have significant operational impact.
|
How will this idea be used?
Client needs a sustainable, operational solution to effectively reset dirty nodes in the live production environment
|
|
What is your industry?
|
Retail
|
|
What is the idea priority?
|
Urgent
|
-
Sep 4, 2020
Admin response
Hi, thank you for your idea. We are targeting delivery of this capability for Q2 2021. The dirty reset will need a time limit coming from a potential SYNC flag or timeout. Which would be preferred? Sync flag or timeout?
Guest
In addition, is there an option for the IV API's to only reset the dirty node settings when there is a positive inventory adjustment (instead of relying on a static Y/N flag to reset the dirty node setting).
Attachments Open full size