I am trying to implement sequential logic in KNIME.
I want the results to be displayed one by one when clicking the Refresh button, but currently, all results appear at once even when multiple cases are processed.
Here is what I want to achieve:
After entering an ID and clicking the Submit button, only table_A should be displayed.
When clicking Select, another table, table_B, should be displayed.
Step 1 works correctly when there is only one widget, but when the Submit button is clicked, both table_A and table_B appear at the same time.
It seems this happens only with tables, as they all display simultaneously.
I followed the instructions in the URL, but integrating the table was not possible.
Below is the workflow I have configured. Could you advise on how to structure it so that the tables appear sequentially as intended?
@JaeHwanChoi I’m not fully sure what your exact use case is, but here is what’s happening:
A Refresh Button always executes all nodes downstream of it.
In your workflow, after the first refresh button, the second Case Switch is always active, so the entire flow continues to run. You need a condition that prevents execution until the second refresh button is actually clicked.
Here is a simple example workflow to illustrate the idea:
For the second refresh button, I added a rule like:
$${Irefresh-button2-counter}$$ = 0 → 0
If the second button has never been clicked, its counter stays 0, so the flow stops.
Once you click the second refresh button, the counter becomes 1, and the downstream logic executes. This approach should help you control the sequence of execution.
