i'm pretty sure if you don't check any then it evaluates all instance, but if you check any then it will only evaluate the checked ones.
Thank you Bill, but I don't think so. Discover rule in the template compares instances of property "TEST1" with a string that is stored in a server property. If it matches, then the component is created for this server and property instance. This works only in case the check mark in the screenshot above is set. If it is not set, then the discover part does not compare all the property instances with the server property and so the discover rule cannot succeed.
We have tested this and found that the check mark has to be set. This is BL 184.108.40.206
What version of bsa is this ? because i don’t see that it’s required and can you show a screenshot of the discovery condition ?
it's BSA 220.127.116.11. See these screenshots for more details:
Custom Property Class "TEST1" with two instances, one with value "123" and one with value "456" for property "my-prop":
Component Template contains a local property of type "TEST1" with name "demo".
Server Property "Description" is set to "123" on a server. This is the result of discover job if the check mark in question is not set:
If the check mark is set, then it looks like this:
So in my opinion the check mark is required. Silly thing is that the check mark is removed with ANY change in the template.
1 of 1 people found this helpful
ok - yeah, so i see what is happening here. i think there are a couple options to avoid this:
1 - don't have any local instances in the template. then it will always evaluate all instances.
2 - have i local instance in the template per instance in the custom class.
"When you check a local property in the Evaluate All Instances of Select Property section, the Component Discovery Job ignores any instances for that property that are defined locally for a component template. If you do not check that local property, the Component Discovery Job uses any local instances for the property when determining whether the target server's properties satisfy the component template's signature."
i've always done #2 because i'm old school and the 'evaluate all instances' box was added recently-ish so i've never messed w/ it.
i would bet the problem you have is similar to rebaselining snapshots - any change to the template clears that field because the change could have been to the local psis in the template so that needs to get cleared. blade just looks for any version change, not a change that would actually require resetting that box.
Thank you for clarification. Option 1 seems to work for BL 8.5+.
At least in 8.3.3 our workaround for the issue will be the removal of any non-read permissions from the relevant templates for our users. This way we hope to be aware of any change and there will be no unplanned removal of this check mark.