Ftyjtk

I've been using the BRE with BizTalk 2016 (FP3 CU5) lots lately. When it works then it's great but I've found trobleshotting problems with policy execution to be very difficult and wanted to check if anyone has found a better way.

I'm using an orchestration CallRules shape to execute the policy. I've also created unit tests that call the policy with a DebugTrackingIntercerceptor. In the case of a successful policy execution, where rules fire, the debug info that's output looks something like:

FACT ACTIVITY 19/11/2018 07:59:12

Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a

Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins

Operation: Assert

Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.GetServiceRequestDetailsResponse:/*[local-name()='GetServiceRequestDetailsResponse']/*[local-name()='GetServiceRequestDetailsResult']/*[local-name()='Customer']/*[local-name()='ContactTransports']/*[local-name()='ContactTransport'][*[local-name()="Name" and .="Email"]]

Object Instance Identifier: 9589157



AGENDA UPDATE 19/11/2018 07:59:12

Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a

Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins

Operation: Add

Rule Name: BartecUpdate

Conflict Resolution Criteria: 0



RULE FIRED 19/11/2018 07:59:12

Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a

Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins

Rule Name: BartecUpdate

Conflict Resolution Criteria: 0



FACT ACTIVITY 19/11/2018 07:59:12

Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a

Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins

Operation: Retract

Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.CreateActivity

Object Instance Identifier: 49478415

Some of the rules within the policy check the value of certain elements of xml document facts. If, the asserted fact happens to have one of these elements missing (such as from the first rule in the activity debug info shown above), then there is no obvious indication of a problem from the tracking info. The only way to identify something's not right is if you notice that the rule did not fire. From here it's a matter of meticulously checking for the presence of elements used in each rule.

Is there a better way to identify why a rule did not fire?