Benefits of using Functionality Criteria

[Kota Kuroiwa]

Behavior, a functionality of ITOM Discovery, is set.
Within that, "Functionality Criteria" can be set.

I can't imagine under what circumstances I would use "Functionality Criteria". If anyone has used it,
please give me an example of when you use it.

Thank you in advance.

Docs：
https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/task....

[Kota Kuroiwa]

Hi @Rahul Priyadars 
Thank you your responce.

I still can't imagine the benefit of using 'Functionality Criteria'.

Narrowing down to Windows port (WMI port: 135) can be set in Behavior.
On top of that, what would be the benefit of using 'Functionality Criteria'?

[Den Masaki]

I have also not grasped the image of 'Functionality Criteria', so let me ask you a question here.

For example, if you want to limit scanning to Windows only, you can use 'Windows Only' in 'Discovery Functionality' to understand that CSS and SNMP will not be scanned.

On the other hand, we would like to ask for further explanation on 'Functionality Criteria'. The document states, "You can use 'Functionality Criteria' to specify a MID server only if you are controlling it in multiple domains."

Does this mean that 'Discovery Functionality' can limit the ports scanned, and 'Functionality Criteria' can control scanning ona per-domain or per-MID server basis within those ports?

I would like advice from anyone who has actually used it.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/task...

[pratik0306]

i just went through the explanation and have same query.. it looks to be for multi domain control but not very clear...