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 Feature
Created by Guest
Created on Nov 2, 2023

Doors Next Needs Server Side Operational Behaviors

In order to add automation to Requirements Management we need to be able to perform actions when an artifact is saved.  This would be similar to the use of preconditions and follow-up actions provided in EWM.

Examples of things we would like to do:

1) Modify attributes of other artifacts (either associated via links or contained within the same module) following the save of an Artifact from the opened Module (most significant Use Case), and from opened Artifact.

2) Prevent saving of an artifact if preconditions are not met (e.g. all attributes are valid in relation to other attributes or workflow state).

3) Create new artifacts, work items, and test cases when an artifact of a particular type is saved in a given state transition.

4) Perform actions based on the change of one or more designated attributes.

While we recognize that some of these actions can be performed via the Client Extension API, we do not want this dependent upon using the UI, as we have command line utilities that perform actions outside the UI and we want the preconditions and follow-up actions to be executed regardless of the interface being used.

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