BMC has a white paper on this. Yes, you can extend the class. Create a new namespace to put the new fields in and give them UNIQUE names. As long as the names do not come into conflict with a BMC field name all will be well. Storage in the new namespace will protect it from most things that an upgrade will do to it. IMO, removing BMC_ prefix will seriously break the ENTIRE cmdb, but it can be done. Instead of renameing the form consider changing the display name to be computersystem. This would give you the same effect, but a minimum of impact You can join the CS to the app forms assuming there is a good key. Be sure not to prefix it with BMC_ and it should survive an upgrade unless one to the two end forms are dropped for some reason.
John Rosquist ----- Original Message ---- From: rey4u <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, May 15, 2008 7:07:06 PM Subject: Cmdb-new class,new attributes hi, Can i create new attributes to bmc:Computersystem form?Will it be deleted during new cmdb upgrade or arserver upgrade? Can i modify BMC_Computersystem to computersystem?what could be the effects? How about creating new join form between bmc_computersystem and bmc_application,so that both the attributes will be in same form?will this will be deleted during upgrade?? please help.... -- View this message in context: http://www.nabble.com/Cmdb-new-class%2Cnew-attributes-tp17264436p17264436.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
