Setting Default Values in Configuration Nodes

[JaeHwanChoi]

Hello KNIME Support Team,

I have a question regarding the use of Configuration nodes in KNIME.

I would like to create a variable configuration dialog using a Configuration node.
In this dialog, I want to display the value a_value, which exists in the column a, as the default value.
The important requirement is:

• The user must not be able to modify this value.

• The dialog should simply display a_value as a fixed, read-only default.

I have tried using the String Configuration node, but it allows users to edit the value.
Other nodes (such as dropdowns or buttons) are not preferred, as I need a simple, read-only text display.

Could you advise which node or approach is recommended to achieve this?

Thank you for your support.

[JaeHwanChoi]

Using Value Selection Configuration or Single Selection Configuration with the selection type set to List is currently the closest solution.

However, this approach highlights the selected value with a blue selection background, which does not look visually appropriate for our use case.

[JPollet]

Hi,

Why not just use a table view node to display a read-only value ?

Best,

Joel

[DanielBog]

Hey,

I would also be interested in the general use case you are trying to solve. If I understood correctly you are trying to display the selected value, but want to prevent your users from editing it?

Greetings,

Daniel

[MartinDDDD]

Given that you are talking about Configuration Nodes I take you want to expose something as read only to the configuration dialogue of a component?

I think what you can try is set the label of a configuration node via flow variable to that value:

No super pretty, but this is what the config dialogue then looks like…chose boolean config as that then just has this check box left (which obviously wont do anything)

Does the component contain views? Is the workflow deployed as a data app e.g. on business hub?

If so you may want to consider @JPollet ‘s suggestion and put the value into a View node (Table View, Text view may be suitable)

[rfeigel]

This may seem pretty lame. Add this warning to the target output node. In any well disciplined organization one should be able to assume that users will follow policies/directions. If not, you have real problems.

[JaeHwanChoi]

Since the values are passed via configuration variables, the table view cannot be used because the execution order between the Configuration node and the Table View node cannot be controlled.

[JaeHwanChoi]

We want to prevent users from changing the selected value and only display the pre-selected value.

[JaeHwanChoi]

Thank you for the explanation.
It is definitely a good approach, but the box that has no interaction stands out too much visually.
We will take this into consideration.

[JaeHwanChoi]

I have an additional question.

Is there a way to immediately reflect values received from a table into a configuration node?

For example, if Table A contains a column “a” with the value “apple,” I would like this value to be displayed in a configuration node.

Then, when Table B is connected, I would like the value of column “a” (e.g., “banana”) to be immediately shown in the configuration node.

Is this possible?

[PanteleyShmele1]

Create a list containing all values you want shown, pass it in as a flow variable into the configuration node

[Geo]

The most basic implementation is to allow a user to change the parameter in the dialog (with a warning description that the parameter cannot be changed) and to set the parameter back to the default value in the backend (within the component) regardless of any user input.