Altinn / Altinn/app-frontend-react

Analysis: Do we need a new view in the app for presenting dataElements linked to the instance

Open
#360 3 comments 1 reaction 0 assignees View on GitHub
kind/analysis org/dat ux
Dominant language
TypeScript
Stars
21
Forks
33
Avg merge
6d 23h
Merged PRs (30d)
3

Description

## Description
During the analysis of Altinn/altinn-studio#7839, a question about needing a new view to present one or more dataElements (PDF etc) is required.
The confirm page brings with it some extra functionality and standard texts that might not be what the app owner require.

Are we in need of a view that is easy to configure where the end user can be presented with PDF or other dataElements for download before the process is complete?

## In scope

## Out of scope

## Constraints

## Ops requirements

## Analysis
One idea is to take the view from the receipt page currently listing the attached documents and make it reusable in a "normal filling page".

## Conclusion

## Tasks
- [ ] Is this issue labeled with a correct area label?
- [ ] QA has been done

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the receipt page that currently lists attached documents and the context from Altinn/altinn-studio#7839. Determine whether its view can support reusable presentation of PDFs or other dataElements before completion. Done means documenting the conclusion, scope, constraints, and concrete follow-up tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.