Message Testing Automation API does not properly transmit triggered Condition Filters to the FE

[chris-kuryak]

Describe the bug

The new Message Testing Automation feature includes a FE page ("Results" page) that shows all of the filters that were triggered. However, the condition filters that were triggered are not successfully being returned to the front-end through the API. In order to complete this feature and meet the MVP requirements, the API needs to successfully return the triggered Condition Filters through the API so they can displayed on the page.

Impact on ReportStream

We are unable to add this Condition Filter to the Message Test result page.

Current response

When a condition filter is triggered, the API does not return the filter that was triggered.

Expected behavior

If a condition filter is triggered during the message testing, it is returned in a consumable format to the front-end along with the other filters that were triggered. It should return in a similar format to the other filters (Jurisdictional, Quality, etc)