Hi, Thanks for the update.. Do I have to create separate normalize job for Product catalogue??
Regards, Pandi.C On 3 Jan 2016 11:07 am, "Jayesh" <[email protected]> wrote: > ** > 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_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
