Tim Yes you could qualify a merge down to even computersystems with a specific categorisation for example.
The identify job doesn't actually merge so the fact they have been auto identified is neither here nor there. -----Original Message----- From: Tim O'Connor <[EMAIL PROTECTED]> Sent: Friday, October 31, 2008 4:49 PM To: [email protected] Subject: Re: Merging of non-reconciled child CIs Romain, So lets say I auto-identify base element, which should give a RE id to all populated instances. That means its also going to auto identify all comp sys instances, basically its just going to dump everything into BMC ASSET; that's what I want to avoid. Now heres a different idea; lets say I auto identify the super-classes of all component child objects. I don't auto-identify BMC_ComputerSystem. Lets say reconciliation finds 5 matching Comp Sys instances in BMC ASSET. Then, when I start the merge could I set it to include Child CIs, but also apply a qualification group to that merge that limits it to class BMC_ComputerSystem? Would that essentially allow only the 5 reconciled BMC_ComputerSystem instances to be merged, along with their child objects? The documentation is so poor. I don't know whether the child CIs would be filtered out of the merge by the qualification group or not. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of P Romain ARSlist Sent: Friday, October 31, 2008 3:23 AM To: [email protected] Subject: Re: Merging of non-reconciled child CIs [The entire original message is not included] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
