ASM servicenow observer to provide improved filtering of data either within the observation or post collection prior to insertion

It's useful because at the moment we have limited filtering in the filer API request, it applies to all classes being discovered and is applied to the API call made to servicenow.  So you get a choice of Include or Exclude, but not the ability to control this down to an individual table or class, ie there could be times when you want to Exclude certain values, but Include others.  As its a binary choice you dont' have that level of control.

Additionally the "Filter resources based on defined JSON attributes" ONLY works if the attribute is present in the data gleaned from servicenow.   There are tables within servicenow that don't contain certain attributes so these are simply left out of the discovered data.  

For example we would like to discover only production devices and within our servicenow this is expressed within the following fields

u_environment_category  and u_environment_type

So i'd like to set it to filter based on  u_environment_category=Prod | u_environment_type=Production | u_lifecycle_status=live,planned,discovered,built,pre-production

But because not every class contains u_environment_category or u_environment_type it excludes discovering those resources completely so i'm stuck just discovering with the u_lifecycle_status attribute.

What I would like it to do is if the resource contains either of u_environment_category and/or u_environment_type attributes then it uses them, however if the resource does not possess it it is still included and not simply not picked up.

What would be more useful would be the ability to specify classes and which filter to apply to the class, ie if we know that a class does not contain the attribute we can tell it to either include or exclude certain attributes and this would be used by the observer when querying for that given table/class.  This would allow greater flexibility so we can get the topology we want and leave out the data we don't.

Or failing that It would also be useful to provide a means that post discovery of resources and prior to insertion into ASM there was an additional filtering capability so we could limit what we insert and throw away the extra data based the ability to specify classes and conditions to either exclude or include them.

This would be useful for all who use the servicenow observer as at present the filtering option is limited and having no control over the service now API call means that servicenow is often not offering the data if the attribute for filtering is not present in the resource.