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
We have noticed in all environments that whenever the Import CDT XML process is run, the Restart WAS Instances process also has to be run due to caching issues. Most times, the environment becomes unusable after an Import CDT. Because of this, in PROD, we have to log a case(PMR) for a restart after each CDT.
Can't the restart WAS be included in the Import CDT XML process, so the Restart WAS Instances does not have to be specifically called? This will also make Import CDT faster in PROD.
How will this idea be used?
It would be relevant whenever configuration needs to be updated on an environment
|What is your industry?||Retail|
|What is the idea priority?||Medium|
|Link to original RFE|