IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling 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
When creating an API dialog there should be an option to continue workflow even when the API fails. Preferably, it would have conditions to continue based upon what error is received.
How will this idea be used?
Use Case 1: This will be used to assign a unique 5 digit number for each activity executed. In order to simulate a loop I have put together a string of APIs and XSLTs with an exit validation at the end to check that everything that needed to run did so successfully. This check will verify that the API completed successfully and push it back to the start if not. Therefore I need to bi-pass the API failure message I receive that stops the process, so that the user does not need to resolve the error each time.
Use Case 2: In SFG, Get APIs fail if a resource doesn't exist. So unless a check duplicate API exists you cannot check if the resource exists from PEM. If PEM had the ability to check the API error returned and continue depending on the error returned this would add really great value.
|What is your industry?||Healthcare|
|What is the idea priority?||Urgent|
|Link to original RFE|