Watson Commerce Ideas

Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Call Center and CPQ are now a part of Watson Supply Chain. Please bookmark the Watson Supply Chain Idea Portal.

Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, Dynamic Pricing, Price Optimization, Promotion Optimization, Markdown and Deal Management. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and IBM experts on the Watson Marketing and Commerce Community and the Order Management Interest Group, now a part of Watson Supply Chain.

Submit ideas for other Watson Customer Engagement Products:

  • Watson Marketing
  • Watson Supply Chain

Let us decide if YFS_INVENTORY_ITEM "select for update" will be used during API calls

For many models, a "select for update" is essential. In our case, our items are tightly controlled, so we do not expect to need to create inventory item records that can then be promised or ordered. We would like to have the choice in findInventory-dependent calls (scheduleOrder, releaseOrder, etc) to override "select for update." It's our data and our risk. If we want a dirty read, that should be our option.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 19 2019
  • Needs review
How will this idea be used?

As a user of the OMS product, the override would let us reduce row level contention for facets of implementation that more correctly fit our model. 

What is your industry? Wholesale Distribution & Services
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files