Skip to content
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

Logical order of custom nodes in workflows #403

Open
loleg opened this issue Oct 25, 2023 · 0 comments
Open

Logical order of custom nodes in workflows #403

loleg opened this issue Oct 25, 2023 · 0 comments
Labels
incomplete Issue needs additional information

Comments

@loleg
Copy link
Contributor

loleg commented Oct 25, 2023

As a user working with custom nodes, it would seem logical to me that the transformation in the workflow editor should happen before the template is applied. However, the documentation examples clearly show that custom nodes need to go at the end of the workflow. And when we change the order in Proxeus right now, indeed the node output is no longer available.

More problematic, and likely linked to this, the output of a custom node is not immediately visible in the document preview. One has to go back to the Documents list and open it again to see the new data.

We need to go through the sequence of frontend-backend interactions (inspect the next call in the Network devtools) and see at exactly which point transformations happen. Then we can see if it would be possible to improve this process - or at least assist the user in creating correct workflows in the UI.

@loleg loleg added the incomplete Issue needs additional information label Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete Issue needs additional information
Projects
Development

No branches or pull requests

1 participant