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 May 11, 2026

When user closes the "Create PDF Document" window in RM before document generation completes, immediately cancel the document generation operation on the server.

Users expect their own jobs to cancel out when they close out of the document generation window (e.g.: while it's waiting for report service availability for a long time).  If the window IS closed out, then there's no path back to the user's browser for the document generation to be delivered to the user.  

As it works today, the RM publishing engine will still process any / all document creation requests submitted to it.  There's no way for those jobs to be cancelled before they begin, (nor for the jobs to be killed once started.)

Aligning application behavior with user's expectations here - killing the job when users close the window - will reduce useless system processing and greatly reduce queue delays during busy document generation periods.  Furthermore, it will greatly reduce the need to pursue "workarounds" such as implementing process fixes or attempting to provide additional information about the print queue to the user base (who generally shouldn't need to know that detailed information, except when things are not working as they expect.)

Idea priority High
Needed By Yesterday (Let's go already!)