Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Future consideration
Categories Usability
Created by Guest
Created on Sep 18, 2025

It would be useful to be able to gracefully break processing in code when bad conditions are detected rather than continue on until critical failure hiding where the issue occured.

There is a lot of error checking that can be done which would allow us to gracefully exit processing with a useful message rather than continue process until some component fails due to the bad conditions. A stop all processing function or a unique throw exception would be ideal which would stop the engine from continuing.. and ideally provide a breakpoint if debugging.

Idea priority Medium
Needed By Quarter
  • Guest
    Nov 4, 2025
    As part of the review process, we strive to be transparent about our intentions with each idea suggestion. The IBM Engineering Reporting team has reviewed the idea, and based on our understanding, it is accepted as an uncommitted candidate.
  • Guest
    Oct 31, 2025
    Thank you for submitting idea. IBM Engineering team review board evaluated this request and determined it will need additional time to evaluate this request.
  • Guest
    Oct 2, 2025
    There are multiple things you can do to stop processing once any error occured:

    1). Use container element's condition script so that It will not get processed on some condition
    2). You can use below thing in Script so that It will print in console that some issue occurred while processing
    throw "ERROR OCCURED";
    From which you can find at what place this issue issue occurred.
    3). There is "Ignore data source configuration errors" [plz set to false, if you want to stop document generation incase of authentication failure] and Ignore Invalid Data Errors [Set to False, It will stop process incase of invalid XML or JSON data that is returned from the end product] option is there in Launcher Metadata.
  • Guest
    Sep 24, 2025

    Hi, when we are processing ETM or DOORS data there are patterns we expect our users to follow so we can code and follow them. These can not easily be enforced with in the products.. for example.. in ETM we expect that when you publish a Test Plan it has all of its test cases contained within test suites.. 

    so when we go to publish the test plan if we find that there are no associated test suites we should stop processing now rather then continue on looking for things we know do not exist so we would like the control to stop processing the template at this point in time rather than cater for all the events that might follow because somethign hasnt been completed correctly. At the moment we have to set variables eg critical_error and have everyblock check for it critical_error == true then dont process and skip to the next block.. this is very clumsy and inefficient. If we could throw and special exception that stops processing gracefully we would know exactly where it got up to rather than parsing the logs to find out where the issue occured. 

  • Guest
    Sep 18, 2025
    Hi Peter,

    Thank you for submitting this idea.
    Could you please provide more details? For example, steps you follow when you get the errors you are mentioning. Type of verification you are talking about.

    Thank you for helping us improve our product.