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 Submitted
Categories Feature
Created by Guest
Created on Dec 18, 2024

Allow getLocksInDatabase(true) DXL Function to Return Lock Information for Locks on Items that the Current User Currently Has Open

The getLocksInDatabase(true) DXL function does not return lock information for locks on items that the current user currently has open.  When I submitted the lack of this function as a bug, the assigned DOORS developer at IBM responded that it was not a bug and that the justification for not returning lock information for locks on items that the current user currently has open is justified in the online DOORS documentation regarding the Tools > Manage Locks functionality which states in part, "The Manage Locks window does not list locks that are associated with your current DOORS session, because you must not delete these locks. If you deleted them you would corrupt your data."

While the danger of deleting locks which could corrupt data certainly exists, there are many other DXL means to delete locks.  Thus, limiting this one functionality does not eliminate the possibility of corrupting data, it only eliminates one possible avenue of corrupting data.  Thus, the constraint of not returning lock information for locks on items that the current user currently has open unnecessarily constrains power DXL developer users.

The requested change will benefit DXL developers in allowing them to more powerfully use DXL to query open modules within the DOORS database.  I use the getLocksInDatabase(true) function to determine who has DOORS modules open so that we may notify users at the end of the work week that they have open modules which if not closed will cause the weekly DOORS backup to fail.  The function currently does not return the modules currently open by the user executing the DXL, leading the user to erroneously assume that he or she does not have any locked modules, when in reality, the user only has no open displayed modules, but may have several open (and locked) modules that are not being displayed.  This may then lead the user to fail to close open modules before the weekly backup.

Idea priority Low
Needed By Not sure -- Just thought it was cool