When an Attachment Category Choice field is configured, the category of .msg attachments is not displayed in the E-mail conversations tab.
The category itself is correctly stored in WFDataAttachmets.ATT_Attribute1, so the information exists and can also be used by SQL queries, actions and other workflow logic.
Example
A mail attachment may have:
ATT_Attribute1 = '<ID>#Giro'
However, when this mail is displayed in the E-mail conversations tab, the user cannot see that it belongs to the category "Giro".
This creates an inconsistency between the UI and the actual attachment metadata.
It becomes particularly noticeable when an Outlook mail is dragged onto an existing attachment. In my tests, the resulting .msg attachment can inherit the category of the attachment it was dropped onto. The category is correctly stored in WFDataAttachmets, but it is not visible to the user in the E-mail conversations tab.
As a result, workflow logic such as a SQL query filtering attachments by category can include this mail, while the user has no indication in the UI that the mail belongs to this category.
Comparison with the normal Attachments view
If the E-mail conversations view is disabled, the .msg files are displayed together with the other attachments.
In this view, their categories are displayed correctly.
So the category information is already available and displayed by the normal Attachments view – it is only missing from the E-mail conversations view.
Suggested behavior
The E-mail conversations tab should also display the configured Attachment Category for each mail.
Ideally, category handling should be consistent between normal attachments and mail attachments, regardless of whether the E-mail conversations view is enabled.
This would make the actual attachment metadata visible to the user and avoid situations where workflow logic uses a category that the user cannot see or verify in the UI.