If the save button has custom handlers to freeze the save action (for background checks or confirmation, as example), the Diagram document gets created before unfreezing / executing the the save action.
When looking at the requests, I noticed that there are some separate upload ones that attach a PNG / SVG file to the Diagram document.
Marius explained to me that there are 3 versions of the diagram document generated at save and that the current approach is not OK. Instead of actual attachments, temporary attachments should be used. The Diagram app should make 2 requests first, to save the temporary PNG and SVG files and then, at save, the two files should be indicated as temporary attachments that must be saved along with the content of the diagram
If the save button has custom handlers to freeze the save action (for background checks or confirmation, as example), the Diagram document gets created before unfreezing / executing the the save action.
When looking at the requests, I noticed that there are some separate upload ones that attach a PNG / SVG file to the Diagram document.
Marius explained to me that there are 3 versions of the diagram document generated at save and that the current approach is not OK. Instead of actual attachments, temporary attachments should be used. The Diagram app should make 2 requests first, to save the temporary PNG and SVG files and then, at save, the two files should be indicated as temporary attachments that must be saved along with the content of the diagram