Expanded explanation of the Image Viewer function

Flow Classic
1

Hi,

I am trying to experiment with using the Image Viewer element in a user step, however I am unable to get it to actually show an image, regardless of whether I attempt to fetch a picture from an online location or locally from the server. The Help-article on Image Viewer (Image viewer | Flow Help) is quite short and lacking examples. Could someone provide som insight on how this is intended to work and perhaps also share best practices for us to link to some internal instruction images that we would prefer to keep internally rather than as publically available resources?

2

Hi Joakim!

There have been previous threads on the subject. Ivan has provided a post in the below thread which I think is what you are looking for :slight_smile: :

File gallery or image viewer - Flow Classic - Novacura Forum

3

Thanks Albin, I actually saw that post, but didn’t want to pick up an old and probably dead thread. While there are relations, it seemed to mix in several topics since it was related to a PDF.

However, I have managed to work around it by experimenting with the wwwroot-folder as suggest. That said, this does not seem like a healthy approach, so I am still left wondering what Novacura would recommend as a best practice for the image viewer and how to best include displayed images in a Flow, and would like to better understand it’s intended use than what is currently described in the Help-section.

4

Sharing images with IIS would work. Not sure I would put it in the IIS root though, better in its own directory.
Depening on the use case, an option would be to put the images out on a 3d party site like imgbb.com.

5

What exactly is not working? What browser are you using? Are you using the old Webclient or the new one or something else?

6

I’m testing this with the latest version of the mobile client for Flow Classic on iOS, however I don’t think the client is the issue. Based on what I can see, I suspect that the image that you link to via http/https is fetched to the server and then forwarded to the client, meaning it is subject to firewall settings on the server (we do not allow unvetted external connections from/to our server environment). I assume this is why a https-URL does not work in my test case, however since the documentation is vague I am unable to say for certain that I have configured it correctly, hence my post.

That said, the workaround suggested by Ola and Ivan to share images via IIS should work for our use-case.