Add the ability to display correlated connectors in a message browser search

[rbeckman-nextgen]

Say you have a bunch of errors on a channel, and you want to find not only the errored messages, but also the associated source raw message that was originally sent into the channel. If you're doing transformation on the source connector, then the destination raw message may not be sufficient information for troubleshooting.

Currently there's no all-in-one way to do that; it's a multi-step process. First you have to search on destination messages with a status of ERROR to get back some preliminary results. Then for each message in that result set, you have to take the overall message ID and do another search using the advanced dialog using that ID. That way you can view the entire overall message (including the source connector) for a correlated ERROR destination connector.

Obviously if you have many such messages to do this for, it can be quite tedious, or not feasible at all. The "simplest" way to solve it (at least in the UI, perhaps not for the actual queries) would be to add a "Always include correlated connectors" option in the advanced dialog, so that if any connector message matched the search criteria, the entire message with all connectors would be returned in the results.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-3160
Reporter: narupley
Created: 2014-02-26T12:52:01.000-0800

[rbeckman-nextgen]

This feature is being requested by one of our clients. One thought we had was that we could search for messages where the response map contained the word 'ERROR'. The problem with this is that once the source posts the message to the destination, the response map contains a status of 'QUEUED' and it doesn't get updated with the 'ERROR' status once the destination fails.

Imported Comment. Original Details:
Author: adriang
Created: 2014-08-07T08:27:31.000-0700

[rbeckman-nextgen]

Most of the time I think users would just want to see the source raw message associated with a particular filtered destination. And this doesn't just happen when you're searching for errored messages, it happens whenever you do any search that ends up filtering only on destination connectors. Like you could be doing a search on the destination response content for a particular message control ID or something.

In the original description I mentioned that we could add an option to "always include all connectors" when any connector matches the search criteria. Another (maybe easier?) solution is just to add an "always include source connector" option, since that would probably satisfy most use-cases.

Imported Comment. Original Details:
Author: narupley
Created: 2014-08-07T08:44:26.000-0700

[rbeckman-nextgen]

The Help Desk has run into this problem several times as well. This improvement would be very helpful! (Latest case # is 29145)

Imported Comment. Original Details:
Author: hdmoscm
Created: 2014-08-19T08:28:51.000-0700

[rbeckman-nextgen]

The use case makes sense, but we'll have to figure out a good way to display the option in the UI if we don't want it to be the only behavior available. I could also see the argument for always seeing the source message if a destination is included, just for traceability.

Imported Comment. Original Details:
Author: jacobb
Created: 2014-08-19T10:44:35.000-0700

[rbeckman-nextgen]

The backend changes that were made to the message browser should make it easier to do this, and we should take a holistic approach to updating the search UI along with all the other message browser updates (hopefully in 3.3).

Imported Comment. Original Details:
Author: wayneh
Created: 2014-12-15T05:29:51.000-0800