Thanks for the quick response. On 5 Jan 2016 4:21 am, "Peter Romain" <[email protected]> wrote:
> ** > > Firstly, be absolutely sure that you need a custom class – can’t you use > any of the out-of-the-box classes? > > > > If not, you can create new classes in Atrium Explorer or, for ease of > migration, you could create a CMDB Driver script to do this. > > > > Choose a namespace of a few characters – you don’t need to follow the BMC > pattern of ABC.DEF unless you plan to create many classes and want to > separate them for some reason. > > > > Also, use a non-BMC prefix for the class, e.g. ABC_YourNewClass > > > > If you create the class ‘legally’ it won’t be affected by future upgrades. > > > > You may also want to create an asset form to make the class visible in > asset management. > > You could use the sync UI function for this but personally I don’t trust > it as it adds loads of unwanted hidden fields and tabs – though I haven’t > tried it in V9. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Pandi C > *Sent:* 04 January 2016 19:09 > *To:* [email protected] > *Subject:* Re: Atrium CMDB implementation > > > > ** > > Thanks for the suggestion.. > > How could create a new custom Class? I have tried & created only the new > Class in BMC.CORE namespace and implemented. > > What is the best practice way to create custom Class? The custom class > should not affected when upgrade the new Atrium CMDB. > > Please suggest.. > > Regards, > Pandi. C > > On 3 Jan 2016 4:11 pm, "Peter Romain" <[email protected]> > wrote: > > ** > > You could use the BMC ADDM product catalog as a starting point if you have > access to it. > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Jayesh > *Sent:* 03 January 2016 05:19 > *To:* [email protected] > *Subject:* Re: Atrium CMDB implementation > > > > ** > > Hi, > > You should have the list of products with manufaturer and model > details.You may get the list > From hardware operations team. > Then refine your list and categorize CTI based on CI type so that you can > import it using DMT. > If you have product catalogue that is changing frequently then you have to > use product catalogue manage data console to update it. So do not expect > full automation 😊 > Once the product catalog is ready,you can create aliases for manufacturer > or model to normalize CI in sandbox datasets. > The ready catalogue is available for ITSM usage but if you have multi > tenant environment then you might have to add all the companies in the > product relationahip to make it visible during ticket creation. > Do not directly import it in Prod. > > Regards, > Jayesh > ------------------------------ > > *From: *Pandi C <[email protected]> > *Sent: *03-01-2016 10:21 AM > *To: *[email protected] > *Subject: *Atrium CMDB implementation > > ** > > Hi, > > We are in the situation to implement Atrium CMDB, the environment already > been installed (on premise & rod). > > Now we would like to configure the data, So we are looking that how to > configure the Product catalogue with relationship of other ITSM modules. > > Can you please give an idea & steps to implement the Product catalogue ??? > > Regards, > Pandi.C > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
