IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. 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. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
How will this idea be used?
Currently there are only two working combinations : [deleteAfterCollect=FALSE + dbCollect=FALSE] or [deleteAfterCollect=TRUE + dbCollect=TRUE].
Meaning either the file is not deleted after collect and not registered in the table FSA_COLLECTED, or the file is deleted after collect and registered in the table FSA_COLLECTED.
It does not meet a common use case where the application want to handle itself the deletion after some functional processes, with the certainty to prevent any further duplicated collect. For this purpose, we do not want to delete the file after collect, but we do want to store the information in the table FSA_COLLECTED : deleteAfterCollect=FALSE + dbCollect=TRUE.
Currently this combination is not working. Meaning the files are not deleted after collect as expected, but the information is not registered in the table FSA_COLLECTED either.
|What is your industry?||Automotive|
|What is the idea priority?||High|
|Link to original RFE|