Watson Commerce Ideas
Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, CPQ, Dynamic Pricing, Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, 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
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Supply Chain
Currently, when calling REST calls, only the StoreId can be used.This feature would allow the store name to be used, in addition to the store ID. This allows for more readability, as it's clear what store the call is being made for; allows for portability, the store name should be the same across multiple environments, but the StoreId may not be. Additionally, for external systems that are calling WCS REST services, it makes it easier for those systems to call.
How will this idea be used?
External clients can call REST services with the store name, instead of the storeId. If publishing many stores, the storeId may not be the same across all environments. Using the Store Name will allow external clients to not change their code to account for this.
|What is your industry?||Automotive|
|What is the idea priority?||High|
|Link to original RFE|