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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
This idea should be revisited.
When someone changes the application XML, a very skinny table MAXPRESENTATION gets updated, and there is no record of that CLOB getting altered at all.
If you enable auditing, you get... a copy of the CLOB and finally the username and date. However, we really don't need the CLOB data, just the name and date.
The value of knowing who last touched a record should not even need justification, and I submit that any IBM employee could provide those justifications for all existing tables today. Where, then is the justification for not extending this to all persistent tables that are direcvtly modifiable by a user (regardless of permissions)?
Thank you for your submission. There are no plans in the next 18-24 months to introduce this change.
Yes, both ChangeDate and ChangeBy are needed together
Agree with the idea of adding both ChangeDate and ChangeBy to all Maximo tables.
If a ChangeDate is added, a corresponding ChangeBy should be added as well.
if this is implemented then the changeby field needs to be added so support staff can use it to identify who modified the record