This workflow demonstrates how to handle file downloads with Selenium Nodes and a Chrome-based browser.
It's a rather sophisticated way of handling a file download which is due to the following points:
(1) Instead of just using a hard-coded download location in the JSON snippet (see Start WebDriver -> Snippets), it will use a system-specific temporary directory to ensure that it works acroess different operating systems
(2) After the download has been started, the workflow will continuously check if the download is still running. This is important especially for larger files. It does not use a “dumb” wait timeout of X seconds, but instead dynamically checks when the download has finished.
The example workflow will go to the Palladian page on NodePit (https://nodepit.com/product/palladian) and download the update site ZIP file. Adapt as needed :-)
URL: Forum Post https://forum.knime.com/t/save-as-windows-file-dialogue-clickable-by-se-nodes/36994
To use this workflow in KNIME, download it from the below URL and open it in KNIME:
Download WorkflowDeploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.