UX: Manual editing of the fields in Table columns config (subform)

[Annikenkbrathen]

Description

As a user, I want to be able to override the texts in the table according to my needs. I still want to retrieve the correct component that should be linked to the table first, but I would like the option to replace the existing text with a custom one.

We chose in the analysis that users should be allowed to select a component from the linked subform to copy settings from, while also enabling manual editing of the fields. This provides flexibility for users to either use existing settings or make custom adjustments as needed.

In this issue, Design need to figure out how this config should look like.

Additional Information

No response

[Annikenkbrathen]

Design suggestion in Figma!

The title changes from showing that we are retrieving the Ledetekst, to calling it "Kolonnenavn" and suggesting the Ledetekst text as the default Kolonnenavn. This allows the user to decide whether they want to change the text. We don't modify the text in the component, but override the text.

The idea is that by calling the field "Kolonnenavn," the user understands that we are referring to the display name in the table and won't be confused about whether they are changing a display name or the actual text key of the component.

Additionally, I have suggested showing which "query" is displayed in the cell, and calling it "Cell Content." This cannot be edited at the moment, but is shown for the user's information and context.

[lassopicasso]

This looks great! 🙂 Nice touch with the default (label) name and the use of toggleable field.
@Annikenkbrathen , do you want more people to take a look at it before it is good to go and start building?

[Annikenkbrathen]

Great, thanks!
Not for me. Perhaps @Ildest would like to look at the content(?) She hasn't worked on the label names with me yet. But you can probably start building a bit until she's back.

[Ildest]

Great, thanks! Not for me. Perhaps @Ildest would like to look at the content(?) She hasn't worked on the label names with me yet. But you can probably start building a bit until she's back.

Thank you, I will take a look this morning :-).

[Ildest]

I have changed "kolonnenavn" to "kolonnetittel" in the sketches @lassopicasso and @Annikenkbrathen. I have a question about the order of things. To me, it seems more logical to set the column title first, then select the things you want in this column. Is that something we have considered here?

[Annikenkbrathen]

@Ildest great!
Yes, we have considered that. The reason it works this way is that we use the label in the component you select as the title in the column title field. So, you don’t actually need to fill in the title, but if you want to change the title that appears there, it is editable.

The title and query fields will not be displayed until the component is selected anyways, I think.

Is the title "Celleinnhold (query)" okay?

[lassopicasso]

@Annikenkbrathen, we currently display the title element regardless of whether a component is selected or not.
Edit: but I can change it so the title (and query) fields are not displayed until a component is selected.

Similar behaviour to summary2:

[Annikenkbrathen]

okey, sonuds good!

[lassopicasso]

@Ildest, @Annikenkbrathen

Is the title "Celleinnhold (query)" okay?

"Celleinnhold" could work, but just for your information - if I understand query correctly, in this context it refers to the data model field used to fetch the value displayed in the column cell.

okey, sonuds good!

Ok, I will hide the title and query elements until a component is selected :)

[Ildest]

@Ildest great! Yes, we have considered that. The reason it works this way is that we use the label in the component you select as the title in the column title field. So, you don’t actually need to fill in the title, but if you want to change the title that appears there, it is editable.

The title and query fields will not be displayed until the component is selected anyways, I think.

Is the title "Celleinnhold (query)" okay?

Thank you, yes, Anniken explained that to me as well, so that´s fine then. We discussed "Celleinnhold (query)" and decided it was ok, since this field is for developers and they use the word query more than "spørring". But in general, if we can use Norwegian terms, we should.

[Annikenkbrathen]

Edit: but I can change it so the title (and query) fields are not displayed until a component is selected.
Did not see this! What do you think Is the best solution? @lassopicasso

I was thinking that since we are going to present both query and kolonnetitle as text that is added, it feels strange to show the fields as open fields that are disabled first (when it’s not required to be filled in/ or edit).
It's a bit similar to the pattern we have on texts when we select a text with a text key, and the ID is displayed below.
You won't need to do anything with the ID field.

[JamalAlabdullah]

Tested ok in dev