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 Space Management
Created by Guest
Created on Nov 20, 2024

CAD Publish and Attach Events are not Logged Historically in the Tririga DB

IBM Ticket - TS016365859

As established in the above ticket, the CAD_DRAWING table stores a row per floor with information like created_by, created_date, modified_by, and modified_date, and is updated any time a user attaches a floor plan in CAD Integrator. It was expected that this row maintained its traceability over time, meaning that if a user created a new floor plan for ABC-Floor1, the created_by would be set to their user, and the created_date would be set to that dates tamp. Then if another user attached the same floor plan later, it would leave the created_by and created_date fields AS IS, and update the modified_by and _modified_date accordingly. This in fact is not how it works today. Today CI will delete the original row and insert a new row every time you reattach a floor plan, meaning you lose the information for who originally created it.


Additionally, we explored the DRAWING_HEADER table. This table stores similar information, but is tied to the Publish events that come from CI, instead of the Attach events. Additionally, this table stores up to two rows per floor, which will always be the two most recent publish events, meaning once a floor plan has been published more than two times, the original publish event is lost.


IBM should either make it be that these tables hold a more accurate account of past events against a floor plan, or create a log table to store this information so that clients may monitor this information accordingly. This may seem trivial, but for large implementations with 40+ CAD users, its imperative to have traceability back to the root of an issue so that it can be addressed quickly and accurately.

Idea priority Medium
Needed By Quarter
  • Admin
    Aanchal Kumar
    Reply
    |
    Nov 25, 2024

    Hello Brent, Thank you for taking the time to provide your ideas to IBM. Our team has evaluated your idea and we will leave it here and review periodically for possible inclusion in a future release. You can encourage others to show support by voting on this idea. Thank you again for your feedback.