Skip to content
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

Codelist improvements #785

Open
1 task
RonnyB71 opened this issue Sep 24, 2024 · 0 comments
Open
1 task

Codelist improvements #785

RonnyB71 opened this issue Sep 24, 2024 · 0 comments
Labels
kind/user-story Used for issues that describes functionality for our users. org/ssb Issues relevant for Statistisk sentralbyrå. status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage

Comments

@RonnyB71
Copy link
Member

RonnyB71 commented Sep 24, 2024

Description

Codelists on Altinn 2 differs slightly from how it's implementet on Altinn 3.

Altinn 3
Current codelist implementation can be either dynamic based on code or static based on json files. Either way they both return the same datamodel:

  • Value (The value to be stored)
  • ValueType (String, Number, Boolean, Null=ValueType not set)
  • Label (The text to display to the user, either directly or as a reference to a language resource)
  • Description (A text to further detail what this entry should be used for)
  • HelpText (A text to be used as a mouse over tooltip)

Altinn 2
This is a bit different that what was the case for Altinn 2:

  • Title (The text to display to the user in the provided language, same as Label with the exception on how language is handled)
  • Code (The value to be stored, same as Value)
  • Language (The language code for the specified code/title)
  • Value1 (An optional value that can be configured to use instead of code)
  • Value2 (An optional value that can be configured to use instead of code)
  • Value3 (An optional value that can be configured to use instead of code)

Differences

  • In Altinn 3 you need to go via the language resource files, while in Altinn 2 you can specifiy the language directly.
  • In Altinn 2 you have 3 alternative values that not only can be used to store, but also that can be used for grouping/sorting/filtering
  • In Altinn 2 there is also the ability to support maintenace via an Excel spreadsheet that can be exported and imported back
  • In Altinn 2 changes to the codelists can be updated without deploying the application, which eases the application maintenance
  • In Altinn 2 you had the option of sharing codelists accross both service owners (global) as well as accross applications within a service owner boundary.

Additional Information

Altinn 2 codelist description can be found here: https://altinn.github.io/docs/tul/funksjonalitet/kodelister/

Tasks

  • Analyse furter the differences between Altinn 2 and Altinn 3 to see if we can have the same support in a new codelist version in Altinn 3

Acceptance Criterias

No response

@RonnyB71 RonnyB71 added kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Sep 24, 2024
@RonnyB71 RonnyB71 added the org/ssb Issues relevant for Statistisk sentralbyrå. label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. org/ssb Issues relevant for Statistisk sentralbyrå. status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage
Projects
Status: No status
Development

No branches or pull requests

1 participant