My questions would be, is there any progress on this topic from KNIME side?
In the meantime I had multiple customers turning away from KNIME because of the missing functionality, and I have another project depending on it.
Is there any other option to share the deployment with consumers where they can not access the workflows and the files?
My another questions would be regarding placing links on the deployment/ ad hoc execution.
Currently I did not find any solution to place working links to download files from the Hub.
On Business Hub there are multiple ways to solve this, but they are not working, since this solution is not a Data App, with the Text widget the HTML is not working, or if i try to point to the Hub files with another nodes, the CHub does not grant access to the file with this “external” way.
Thanks for reaching out! We’re actively working on making Data Apps available on the Community Hub Team Plan, and the release is planned for March. So you won’t have to wait much longer!
Deploying as a Service is also planned to be available soon or only schedule and data app is the current scope of CHub?
I remember this node, back then in August, i was experimenting with it.
I dont remember the full error code, the node worked fine locally or on Business Hub, but not on Community Hub.
The error message itself were suggesting something like the node or the CHub does not support that type of path variable, like the node accepts only A nd B type of variables, and the CHub accepts only C or D. (we tested out all possible referencing methods)
However, thank you, probably its something that was fixed in last year, i will check it.
REST deployments will also be available on the Team Plan soon. So stay tuned for that!
Thanks for sharing your experience. If the issue you encountered back in August persists, feel free to provide more details, and we can look into it together.
Hi Victoria, I did a basic test with the widget, uploaded a sample workflow.
The same error message when running on AP or on CHub
Also tried:
-convert path to string, then convert string to path (relative, instead of connected)
-path to uri
both cases the node fails becuase the path/uri points to a non existing file or is outside of the workflow.
Thanks for testing it out! You need to first upload the file to the data folder within the workflow and then pass that path to the Download Widget. The Transfer Files node helps you to move it from the space to the data area.
Let me know if you need any further clarification!
