-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✅UX Design : for component overrides configuration #13622
Comments
We could think of something like "Tilpass komponenten" and revise any texts/tooltips that are included? |
I'm putting this in blocked as Domain 2 isn't working on Summary 2 yet this sprint, and I have other tasks to do first. I will pick this up when I get the chance. |
I've tried my hand at a design here. I believe I've covered all the true/false scenarios, but I may have missed something. I've tried to simplify it as much as possible, so I've set some options to false when another switch is turned on to reduce the number of choices for the user. However, this is a bit risky, so I may have overlooked something. I'm not very familiar with the code terms behind this, so there was some guessing involved when I rewrote it. I'm sharing a video so you can see the interaction, along with an image showing how I think it connects with the overrides in the code. FYI @framitdavid Click on link to see video 🎥 |
@framitdavid do you have time to check if this design covers all overrides? |
Great, this looks good. I see that Regarding "Vis tomme felter," I believe it is "on" when it is not set. The property in the configuration is called Ref. docs: https://docs.altinn.studio/nb/altinn-studio/reference/ux/components/summary2/#overstyringer |
I don´t have enough background/context to understand this properly from this issue alone, but I can look at it with you @Annikenkbrathen if there is still time. My initial input is that I would try to use either only "oppsummering" OR "sammendrag" in the texts, not both (unless these are two different things), and I would probably find some other way to phrase "overstyr", as it is sort of technical, and I think we may be able to tell the user what to do without using that term. |
Yes @framitdavid we can look at a help text here. I need a briefing on the scenario, as this whole issue is new to me. |
@framitdavid Gørild and I discussed this again today, and we were a bit unsure if we misunderstood your comment regarding When would
|
Forslag: "Du kan bare skjule tomme felter i oppsummeringen hvis de er valgfrie". "Du kan bare skjule komponenter fra oppsummeringen hvis alle feltene er valgfrie". |
READY TO DEVELOPE! The new addition to the design is an info message explaining that required fields will not be overridden. The message only appears when relevant, such as when the user enables "hide component" or "hide empty fields. |
Tested ok✅ |
User Story
As a user, I need a clear and intuitive interface for configuring component overrides, so that I can easily add, edit, and manage overrides for my components without confusion.
Specifications
The UI should allow users to configure overrides for multiple components within a page or group component. It should support adding and removing overrides.
UI Requirements
componentId
field.hidden
,forceShow
,emptyFieldText
, andhideEmptyFields
.hidden
cannot be combined withforceShow
. We should make it easy to do right.Text Content
Should we somehow in the studio explain what this property does or link to a how-to-guide? 🤔
Components Overrides
Here are the common parameters that should be included in the UI:
componentId
hidden
forceShow
hideEmptyFields
is set to true in the summary componentemptyFieldText
hideEmptyFields
Link to docs for more information:
https://docs.altinn.studio/app/development/ux/components/summary2/#overrides
Acceptance criteria
The text was updated successfully, but these errors were encountered: