Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Categories Workflows
Created by Guest
Created on Aug 31, 2018

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.  

What is your industry? Healthcare
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.

  • Guest
    Jun 24, 2020

    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

2 MERGED

Resolve Error must re run the API which failed

Merged
Hi Team, As per the current process, the Resolve Error will re run from the first API present in the Task, rather than coming from the API which got failed. It would be better, if we can have this Resolve Error Option to run it from the API which ...
over 2 years ago in Partner Engagement Manager / Workflows 1 Planned for future release