If I understand what you are asking; you want to move away from "include
collection" and "exclude collection". You can certainly do so--it's how we
"used to do that" type of thing in CM07.
for "include collection" -- either use the exact same query you used in the
other collection; or you can use the WQL trickery to do the exact same thing
that 'include collection' is doing; just not as pretty to read.
for "exclude collection", you'd need to use a subselect; something like..
where resourceid Not In (select resourceid from <all the parameters and values
you used in the collection query for which you want to exclude those types of
machines>).
It's up to you what makes the most sense.
Is there some problem you are trying to solve? is the problem technical
(resource constraints on evaluating collections) or is the problem report
related (keeping track of all the relationships between collections) ?
On Tuesday, January 26, 2016 8:24 AM, Kevin Ray <[email protected]>
wrote:
Hi Team,
What is the practices when creating the collection , If we want to include or
exclusion of some collections ?
1 ... Can i directly add inclusions and Exclusions --
--- Like these in my environment we have many collections where it has
refereed to some other collection(many collections have reference collections)
2. Instead of creating like above..If we create WQL instantly when we are
creating the collection will it make sense ?
Or any other better way ?
