Create a receipt page with standard display for an app

[helenekri]

Functional architect/designer: @-mention
Technical architect: @-mention

Description
For MVP we need to have a standard page containing content for the receipt page.
-It should be decided if this should be a part of the plattform or service specific
-What do we need to have as content

This issue has been updated because of the solution described in #926

Sketch (if relevant)
https://www.figma.com/file/O7Oqx6p9ZUZBt8DFBNanrymh/MVP-2-Altinn-Studio?node-id=1567%3A60617

Navigation from/to (if relevant)
This functionality is reached from...

Technical considerations
Input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criterea

• The receipt page is part of the platform
• The receipt page should look the same as the receipt the end user finds in his Altinn inbox. The design is described in Figma sketch and issue Archived instance receipt page for end user - Accessed from messagebox/inbox - Archive #2110
  • Except a text telling the user that a copy of the receipt is in his Altinn inbox.
  • A green background color (#D4F9E4) top header of the modal should use darker green (#17C96B)

Out of scope
E-mail (post-MVP)

• This has been set to post-MVP. Handled in issue As an end user I want to receive a receipt by e-mail app-lib-dotnet#320
• We should implement a button for sending the "receipt" to another e-mail.
  • This functionality should reuse the same page as Altinn.no
• The actual download of a PDF of the APP is covered in Print-out generation PDF MVP3 #1389

Tasks

• Find out if the receipt content should be part of plattform or service (requires a decision between technical and functional

• Find out what we need to include on the receipt page (print-out, reference number, information text etc)

• Design how the page should look (with regards to content)

• Implement receipt component

  • Include receipt component in workflow step

• Implement the design

• Update documentation (If required)

• Write jest tests

• Documentation

• Test - Trymen

[GGunnar]

@Febakke This EPIC needs User Stories which we can break up in which we can start developing right away and area which need to implement after the blocking issues are resolved. Evaluate also if those blocking issues, should be moved to the relevant EPIC.

[IneF]

@Febakke is this really blocked by Add PDF-Generation functionality in Runtime? We should be able to create the page, but the PDF functionality will not be complete before that part is complete, but that should be stopping the PDF-Generation issue and not this issue.

[GGunnar]

Closing this EPIC as all user stories and tasks are closed.