Leap Version: 9.3.3
Leap Deployment: Standalone
Operating System: Oracle
Problem/Query: Images pasted in the Rich Text Editor work initially but then seem to lose their connection to the attachment and won’t render after saving, just showing an image placeholder:

The source shows: /forms/secure/org/data/86b6c8f9-17fb-42a7-8a06-2b56f1cbbdb8/F_Form1/attachment/88c048cc-ada6-4c73-a241-d965fb6139d5/image.png?dbid=561718
Hi Jon,
This issue is very similar to a case I am currently working with a customer and created this defect article on it;
In this case the issue is that the path to the graphic is being sent instead of the actual graphic. The path that is being sent in the email is the same as you are seeing in your issue. HCL development is working on a fix for the next release of HCL LEAP and HCL Domino LEAP. I would suggest you get a case opened with support so we can check and see if it is the same issue and if so make sure your use case is covered by the fix
1 Like
We are working on a fix; however, it might have limitations.
There seems to be no reliable way, for all common email clients, to embedded an image into an email. The suggested best practice is to use URLs pointing generally-available resources. The implication is that any URL that points to an image that is part of the submitted data, means that that the submitted data needs to be accessible anonymously. A 2nd implication is that doing this would exposes the hostname and app uuid to those who might not have known it before, and perhaps shouldn’t know it.
Jon, I’m very curious to understand your use-case.
Good Afternoon. We are not actively concerned about how this shows in email, my problem is if someone puts in a picture in the Rich Text Field today and comes back tomorrow, the image is gone. So even within Leap it appears the attachment is going away.
We are using this specific Leap application to replace a Word based review and approval process, and part of this requires graphs and charts to be embedded in the write-ups.
I am meeting with our admin tomorrow to get an official ticket opened to hopefully be able to pass along more details/examples.
ok, thanks for the clarification. This is clearly a bug and we’ll address it through the support ticket.