You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If an existing workflow is opened for editing via Kitodo and then saved again without making any changes to it, the corresponding workflow .svg will end up being 0 bytes in size and therefore empty/broken.
This only affects the svg image file, the workflow itself remains unchanged. (The file is only rewritten, which can be recognised by the modification date of the file)
To Reproduce
Steps to reproduce the behavior:
Go to 'Project' --> 'Workflows'
Open an existing workflow
Do NOT make any changes to the workflow and save it
Workflow is saved without an error message
Determine that the associated .svg file is empty / 0 bytes in size
Apart from the filesystem, you will also notice this in the corresponding process template when you unfold it
Expected behavior
Saving workflow without changes should also result in a functioning .svg file
Workaround
Open the Workflow
CHANGE anything in the workflow (for example remove and readd "end")
Save the workflow
A new correct svg file should be generated
Screenshots
Release
Tested with 3.7.1
Desktop (please complete the following information):
OS: Kubuntu 22.04
Browser Firefox
Version 132.0 (64-bit)
The text was updated successfully, but these errors were encountered:
Describe the bug
If an existing workflow is opened for editing via Kitodo and then saved again without making any changes to it, the corresponding workflow .svg will end up being 0 bytes in size and therefore empty/broken.
This only affects the svg image file, the workflow itself remains unchanged. (The file is only rewritten, which can be recognised by the modification date of the file)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Saving workflow without changes should also result in a functioning .svg file
Workaround
Screenshots
Release
Tested with 3.7.1
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: