I guess that if you never want to upgrade this system then you can do what you propose.
An alternative to the class manager would be the cmdbdriver which, in my experience of early versions of the cmdb, was more reliable. If you have a test system then you could create a cmdbdriver script to change all the names there and, when you're happy, you can simply run it on the production system. If you only have the CMDB then the forms you will be editing on the specifications tab could be overwritten during an upgrade but you should be able to recover customisations (display labels and form layout) by exporting the forms before the upgrade. Cheers Peter From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Frank Caruso Sent: 08 July 2011 14:57 To: [email protected] Subject: Class Manager for CMDB 1.1 ** ARS 6.3p24 CMDB 1.1 Oracle/Solaris Situation The CMDB has been extended with the addition of two new classes. They are both regular classes with an abstract class as their superclass and that abstract class has BasesAsset as its superclass. The two new classes were copied for BaseHardwareSystemComponenent and there are many fields on the Specifications tab that we want to rename - display and database value. I know this should be done through the class manager but am fearful of whether it will work. We are an unsupported of Remedy, do not use the CMDB for reconciliation or configuration management and never will. I am thinking about just renaming the fields directly from the underlying forms. Thoughts? Frank _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
