FailedMessagesView: When message types are not present in the metadata from SC, then SP must display proper default values instead of NULL_TYPE

[indualagarsamy]

For external integration scenarios when 3rd party systems are sending messages to NSB endpoints, they may not contain the EnclosedMessageTypes header.

When SC parses this information, the meta data for MessageType will be null.
We need to set proper value such as Not available - missing metadata EnclosedMessageTypes or something of the sort.

Relates to Particular/ServiceControl#429

[gbiellem]

@indualagarsamy - this will be addressed as part of https://github.com/Particular/Requirements/issues/194 correct?

[indualagarsamy]

@gbiellem - that's correct. we should.

[weralabaj]

This is how it currently looks like, seems like it was fixed as part of something else. Can we close this one? Or do we want do display different text, rather than "unknown"?
@gbiellem @indualagarsamy

[gbiellem]

I'd prefer a bit more detail like Message Type Unknown or @indualagarsamy's suggestion of Not available - missing metadata EnclosedMessageTypes

[weralabaj]

Ok, I'll go with 'Message Type Unknown - missing metadata EnclosedMessageTypes'.

[weralabaj]

@johnsimons that was done as part of 194, was merged and can be released independently of SC changes. Can be closed.

[johnsimons]

Fixed in cee57dc