A customer would like to use the EDANS application to integrate SNOW with EDA but has worries that too many events will be sent to EDA due to the nature of there being no filter on the EDANS app.

This customer needs the ability to limit the application to only sending specific categories of events found in the Catalog Request, Incident, Problem or Alerts tables.

In lieu of building a complete “condition builder” in EDANS - it was suggested that the SNOW native “Business Rules” facility could be used as a source of events that feed the EDANS. In this way, the customer could use the native “condition builder” present in the Business Rules GUI of SNOW, to feed specific (filtered) events to the EDANS thus limiting the number of events sent to EDA.

This would also allow the customer the opportunity to *not have to write and maintain Javascript scripts that build the event payload in SNOW and manually send them to EDA.

See the SNOW native Business Rules screen shot attached.