Is it still recommended to use quickforms nodes?

[tbtt]

Hello,

is there any replacement for the Quickforms Input Nodes? I try to add parameters to my KNIME Workflow via KNIME Rest, I made it work using the String Input Node.

Is it still recommended to use the Quickforms Nodes?

Best

[ipazin]

Hello @tbtt,

Quickform nodes are legacy and there are replacement nodes. Widget or Configuration nodes depending on use case.

See following topics for more info:

Component Order

In short, Configuration nodes are used to parametrize workflow and appear in the component configuration dialog (the one that opens on F6 or double-click on a component), while Widget nodes are used to define interactivity in the workflow and they appear on the WebPortal/Interactive View (the one that opens on F10 or right click->Interactive View). So the functionality of the deprecated quickforms is split between these two new node categories. Let me answer your questions one-by-one: As far …

Configuration vs widget nodes

After upgrading to knime 4.0, I’m struggling to understand the difference between configuration nodes and widget nodes, I.e. column filter configuration vs column filter widget. Could someone elaborate please as I can’t find any documentation about these. Thanks, Simon.

Br,
Ivan

[tbtt]

Hey Ivan,

thanks for your reply. Actually I am still not sure if the Configuration or the Wigdet Node should work for REST Parameters (I tried both and neither worked).
The topics you posted talk about the differences between the nodes but I didn’t find any information about which new node to use for REST parameters.

[ipazin]

Hi @tbtt,

are you trying to execute workflow(s) on KNIME Server using Call Workflow nodes?
If so you should use Container Input (JSON) node.

Check these workflows: https://hub.knime.com/knime/spaces/Examples/latest/06_Control_Structures/07_Workflow_Orchestration/02_Call_Workflow_and_REST/

Does this help?

Br,
Ivan

[tbtt]

Hey ivan,

I am trying to execute the workflow e.g. via Postman URI like this with a String Input Node works:
....rest/v4/repository/test:execution?string-input="true"

With either of the the two new nodes (Widget and Configuration) the list of possible parameters is empty, error message:
org.knime.core.node.InvalidSettingsException: Parameter name "string-input" doesn't match any node in the workflow, valid parameter names are: []

When I use a Container JSON Input Node, it works but doesn’t seem intuitive for passing just a string, also I lose the RegEx checking which is available in the String Input node.

Best Tim

[ipazin]

Hi @tbtt,

I see now. There is a ticket (internal reference: AP-14404) to support Configuration nodes in this case. Will give it +1 from you.

Note: Changed category to Server.

Br,
Ivan

[tbtt]

Hey Ivan,

thanks!
So using the legacy nodes seems like a legit choice in this case for now?

Best

[ipazin]

Hi @tbtt!

Ok. Checked a bit more. Quickforms are not recommended rather one should use Configuration and Container Input nodes. In order for Configuration nodes to work you need to create a job and then add defaults to parameters and execute. Now calling this job should provide parameter names from Configuration nodes.

Br,
Ivan