IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Allow Workflow to Continue After API has Failed

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.  

  • Guest
  • Aug 31 2018
  • Planned for future release
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
  • Attach files
  • Guest commented
    24 Jun, 2020 09:46am

    Another example: using an API to both retrieve data e.g. api.companieshouse.gov.uk/company/{company-number} and also validate {company-number} if I get HTTP 200 I want to continue but if I get HTTP 404 I want to be able to specify a different Response JSON format so that I can retrieve the error message as well as pushing the user back to restart the task/back to the previous dialog so that I can both show the user the error message and get them to correct the error without needing a sponsor user to intervene