Display attached PNG files in report without Base64 embedding the file

Currently, images can be displayed in the WATS Report by performing a Base64 encoding and embedding it in the "Report Text" using img tags etc. (as described here: Include an image or link in the UUT report – WATS Support Center). 

This works (great), however the image data becomes part of the report XML and therefore contribute to the data usage on the WATS subscription, even if the WATS server is setup with a "Blob-storage" option (which enables storage of attached files without hitting the WATS Test plan data usage). 

It would be nice if, for a subset of types or only for PNG files, the Report viewer would display attached png files even without embedding the data in "Report Text".  

This would allow our vision test stations to display relevant visual test proof in the report while still using the blob storage for handling the image data.  In our use-case, we capture pass/fail using boolean step but we cannot embed the image data in report text because it would cause Gigabytes of image data to be counted on our test analysis data usage.  Attaching them as files works (of course), but then the people reviewing or auditing reports have to click and download/open files as separate steps, instead of being able to see the images directly in the report. 

It should be possible (for WATS development team with backend access) to generate suitable <img> tags that use the blob-storage url and in that way show attached image files that are "attached as files".  For end-users this seems not possible as the blob url is not known at the time the step-fields are filled. (Otherwise we could probably have inserted the html code ourselves).

From a content validation stand-point, doing it simply based on file extension = png ads no more risk than letting us pass in whatever base64 encoded strings we choose, so maybe it would be acceptable that it only process .png attachments in that way, and that it does not do additional verification on the file? If file content is corrupt/wrong, it just wont display as an image (so maybe also add alt-text in the img ref tag).