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

Support for multiple data models in layoutset/task in Studio #12515

Open
nkylstad opened this issue Mar 15, 2024 · 1 comment
Open

Support for multiple data models in layoutset/task in Studio #12515

nkylstad opened this issue Mar 15, 2024 · 1 comment
Labels
Epic Used by zenhub to identify the epics that group issues. team/studio-domain2

Comments

@nkylstad
Copy link
Member

nkylstad commented Mar 15, 2024

No description provided.

@nkylstad nkylstad converted this from a draft issue Mar 15, 2024
@nkylstad nkylstad added the Epic Used by zenhub to identify the epics that group issues. label Mar 15, 2024
@nkylstad nkylstad moved this to 📈 Todo in Team Studio Apr 22, 2024
@nkylstad
Copy link
Member Author

Which data types should be possible to select in a data model binding selection?
Limit data types with app logic.

  • We should use datamodel specified in layoutset as default.

    • What should happen if the user switches data type associated with layoutset?
      • Validation that default data model (the one specified in layoutset) matches with old data model bindings
      • Warning message about the consequences
  • Should be possible to view datamodelbindings with old setup

  • Should be possible to edit dmb with old setup - this will convert to new setup

  • Should have a default selected data type

  • Should be possible to change data type

  • Should it be possible to select a default?

  • Should replace the data model (native) select (in process task config) with Combobox

  • Endpoint to fetch available data types (with appLogic) - already exists, but is filtered - boolean?

  • Endpoint to set data model for process task should support array of dataTypes instead of single dataType

Example app using new structure: https://dev.altinn.studio/repos/ttd/multiple-datamodels-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Used by zenhub to identify the epics that group issues. team/studio-domain2
Projects
Status: 👷 In Progress
Development

No branches or pull requests

1 participant