IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
In v12 entities have e-tags so knowing if it has changed can be done using e-tags, one can, through REST API, even ask to return a process for example only if it has changed based on its e-tag using the if-not-match header.
That aside, IMHO GIT integration would be the way to manage 'source' for a model and moving, in a controlled/governed process, from DEV to TEST, UAT and PROD. If one uses GIT that way one would have all these details, apart from being able to group changes, manage versions, and promote them obviously.
TM1 v12 uses a bare GIT repository behind the scenes to store all metadata. Perhaps we could define a vocabulary that could be used to annotate entities in responses with version related information which could include the date time stamp at which a commit was made.
It's a bit odd the Turbo Integrator processes do not include a last updated property. I've changed this to future consideration and will track a work item to add this.