-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] New workflow visualizer in the UI does not fit the whole workflow diagram and cannot be scrolled to see all of it #343
Comments
Was digging a bit more looks like the problem comes from the https://npm.io/package/orkes-workflow-visualizer/v/1.0.0 library that has a fixed width of the canvas set to 2000. While the height is adapting to the workflow. |
We've found this. It looks like the component should allow for horizontal and vertical scroll but doesn't honour the settings. |
Thanks for reporting. We are on it! |
updated orkes-workflow-visualizer version to 1.0.1
[#343]fix:workflow diagram canvas width issue
confirmed its working @najeebkp thanks! One improvement I would like to see is when opening the diagram that the view is horizontally centered, this is because the workflow |
Describe the bug
With the implementation of the orkes-workflow-visualizer in the UI, it is no longer possible to see large workflows that are wider than the hardcoded width of the visualizer. It is not possible to drag the workflow visualizer like in the previous visualizer and it is not possible to scroll to see the whole workflow.
Details
Conductor version: 3.21.11
Persistence implementation: Postgres
Queue implementation: Postgres
Lock: -
Workflow definition: see attachment
Task definition:
Event handler definition:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to be able to see the full workflow visualization and be able to click and drag to see the whole diagram.
Screenshots
If applicable, add screenshots to help explain your problem.
bug_report_wide_workflow.json
The text was updated successfully, but these errors were encountered: