A very exciting observation. If so, this would be a fatal change, especially for bmc Discovery, because operating systems always have a version and without a version rollup it would be impossible to normalize it cleanly and easily.
I don't have an 18.xx Ar system with us yet, but bmc often just creates new interfaces and lets the backend forms often exist. Have you ever checked if the form and the entry for the product class are still there? If yes, you could create an entry for the class operatingsystem and see if it works.
This is no guarantee, but I would be much calmer
Gustavo del Gerbo As a normalization expert, can you clear this up and calm us down? It's just a documentation error, right?
1 of 1 people found this helpful
I want to be able to rely on the information in the BMC DOCS.
Should BMC not be able to release a new version of the application without updating the documentation?
By the way: yes, it still works as under version 9.1!
good to know, at least now I can sleep more quietly again.
Of course you're right, the documentation should match the version and be up to date.
2 of 2 people found this helpful
Sorry it seems I got a little late to the conversation.
I see were you got confused:
- Version Rollup rules apply to CIs in the BMC_Product class.
This is just a definition of what is shipped by default. But as you can further see in the DOC page it mentions that you can chose the classID for the rule.
I have commented this to DOC team so that they can clarify this.