Hi,
I have created several event rules to bind to CIs depending on the required filters. What I am seeing however is an extra field being used in the CI bind that is not configured in the event rule used, nor in any event binding scripts. The extra field is a custom field I have created but is not relevant to the binding to the CI Type. Using Check Processing of Event link I can see it hits the right rule, but what I would like to see ideally is a debug of what the event processing is actually doing and why it is picking up this non-relevant field to use for binding to a CI.
I know the Event Rules work as I have exported all rules via an update set and imported into a fresh developer instance and tested. The rules work as expected and bind to the expected CI.
So my questions are, what else could be influencing the CI binding process to include this field in the evaluation and is there some way of debugging the event processing?
Thanks
Jon
