To reproduce, with Form Runner setup to use a RDB (say MySQL):
In Form Builder, create a form a/library, add a static image, publish it. Create a form a/a, add the section template, publish it, load a/a/new ⇒ all good.
Update a/library, change the image, publish it. Back to a/a, click on the green reload icon to update the section template ⇒ the image shows broken (404).
The 404 is because we try to retrieve the image with version 1, while it is stored as version 2 in the database.
Since we embed the section template into the form on publish, we should also copy attachments part of the section template where we store the published form (crud/a/a/form/123.bin), as the published form shouldn't have a dependency on the published section template (crud/a/library/form/123.bin).
I would suggest that, when in Form Builder the template is added or updated (not when publishing), we copy attachments part of the template along the form data. This way they will be automatically copied in the right place, and with the right version, when the form is published.
To reproduce, with Form Runner setup to use a RDB (say MySQL):
a/library
, add a static image, publish it. Create a forma/a
, add the section template, publish it, loada/a/new
⇒ all good.a/library
, change the image, publish it. Back toa/a
, click on the green reload icon to update the section template ⇒ the image shows broken (404).The 404 is because we try to retrieve the image with version 1, while it is stored as version 2 in the database.
Since we embed the section template into the form on publish, we should also copy attachments part of the section template where we store the published form (
crud/a/a/form/123.bin
), as the published form shouldn't have a dependency on the published section template (crud/a/library/form/123.bin
).I would suggest that, when in Form Builder the template is added or updated (not when publishing), we copy attachments part of the template along the form data. This way they will be automatically copied in the right place, and with the right version, when the form is published.
+1 from community