This is an IBM Automation portal for Cloud Management and AIOps products. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Up-issuing a Definition should automatically up-issue any Rule and/or Policy which calls it
ITNCM Compliance manager has a feature whereby once you "activate" a Policy, Rule, or Definition - the version number of that Policy, Rule or Definition is automatically incremented whenever it is edited. It is normal to have each Policy call one or more of Rules, which in turn may call one or more Definitions. The way ITNCM works at present, if a Definition is edited (and hence it's version gets automatically incremented) this has no effect on the version number of the Rule which calls it and the Policy which calls the Rule. It is not obvious by just looking at the Policy that anything has changed. If (as we are) you are developing Policies etc. in a lab environment, for export to a number of production instances of ITNCM, this makes it extremely difficult to maintain version control. The policyExport utility permits a particular version of a Policy (and all Rules and Definitions it calls) to be exported - but at present, if (say) a Definition is updated, there is no indication that the Policy has changed in any way. If we want to convey this by changing the Rule and Policy version we have to do it manually- which is time consuming and prone to error. This enhancement request is for the incrementing of the version number of any Definition or Rule to also automatically increment the version number of any Rule or Policy which calls it. (This should also be extended to extractions etc.)
Do not place IBM confidential, company confidential, or personal information into any field.