Possible to design a confirmation view

[TheTechArch]

Description

For some application owners, it is better to show a designed view of the data and not pdf. See Altinn/apps-backlog#1

Screenshots

Considerations

If we introduce a "confirmation view" design capability this might be used as input for a "receipt generated". This should be input to a more general "Do we need PDF" discussion.

• Is there any need for components updates to be presented in this view?
• Can this be solved as a backend functionality? Generate HTML based on the layout and data and save it as data just like PDF?

Unanswered questions

• PDF support in old generator?

Altinn Studio

How can we add designer capabilities for different tasks?

How can we map design to a given data model? Do we need to? Can we make the assumption that it is a data model for the previous data task?

What if the previous task had several data elements?

Ops requirements

Are there any requirements for monitoring? What is being built and what could go wrong? Are there any requirements related to backup?

Acceptance criteria

• Possible to design the confirmation view with the elements?
• Still possible to save something that can be used as proof?

Specification tasks

• [ ] Development tasks are defined

Development tasks

• [ ] Add design capability in UI designer from another task
• [ ] Update Confirmation view to support uilayout
• [ ]

Test

Add test cases here as checkboxes that are being tested as part of the changes.

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)