pre-defined BCM BIA Element Definition Filtering not working for BIA

[JBIV]

When I set an element definition filter (any table, any element, any filter) it does not work as the BIA template spins up to filter out items (e.g. Application Services filtered only to Environment = Production) when choosing an "Applies To" item.  However, the source table is set and the ad-hoc filter when setting up a BIA in the workspace works for any filtering used on the applied to list if you do it when populating the basic BIA info  (i.e. name, template, BCM Lead, Applies To). 

This is across all our instances and a PDI installed to the same versions as we are currently (Washington Release.  Latest Plug-ins available installed.).  So, it appears to be an OoB issue (at least to Washington).  Any ideas?

[Vishal Jaswal]

Hello @JBIV 

Yes, that is the expected out of the box behavior. 

If you want some specific table to be autopopulated in the table name (screenshot above) then I would recommend to create your own template.

[JBIV]

Hi Vishal - I wasn't clear.  it is not the table that is the issue.  The table (in this case Sevices [cmdb_ci_service] comes in as it is defined for the specific Element Definition.  It is the prefiltering of the elements themselves that is not working (see example filter). 

This should filter down to all application services which are operational and production (on the CMDB_CI_service table).  However, instead it just shows everything on that table when I go to actually spin up a BIA using the template defined with the element definition.

Please note, have now tried it in a Washington PDI and a Yokohama PDI and filtering does not work for either if done on the element definition.  it will work if done each time you go to setup the actual BIA.

[Nikhil Bhalla]

Hi, I'm facing the same issue. Did you find a solution/workaround to this? Thanks

[JBIV]

Unfortunately, no.  We escalated through to ServiceNow support and they reconfirmed this is expected behavior.  For us, if we are doing a large level of new assessments, we ultimately do a data load to the bia table to "set them up" and then make them available.  It's less than ideal but works well enough for annual processes.