Improved summary and PDF experience

[olemartinorg]

There is a need to improve the existing summary functionality including the PDF in order to meet new requirements, to catch up on existing bugs and feature requests as well as to improve the code base.

While the a summary page, and especially the Summary component, is the main foundation for the PDF, there are also separate improvements needed for PDF that is independent of the Summary component. This epic address the total of changes needed in order to meet customer expectations.

Design for the improvements will be handled in #1744

Summary component

Right now our Summary component is somewhat limited. It is possible to point it at a single component, a non-repeating Group, or a repeating Group component, and if my recollection is correct it will:

• Display a simple value, as typed/selected in the target form component
• Display a static map for the Map component
• Render non-form components as normal (or not show them at all?)
• Render a non-repeating Group as a condensed/compact summary
• Render a repeating group as a condensed/compact summary, but will not render nested repeating groups by default
• Render a repeating group looking like individual fields, and render nested repeating groups as condensed/compact fields if given largeGroup: true.

It will however not:

• Render a summary for an entire process step, or a different process step (although the automatic PDF generator will attempt to do that for the current process step)
• Render a summary for an entire page, unless that entire page has been wrapped in a non-repeating Group.
• Render deeper components. If given a Group with a Grid/Group/container component inside of it, the innermost container component will not be rendered, as summaries are not recursive.

At the same time, configuration is somewhat limited, as we allow for the excludedChildren and display options, but it is not at all easy to wrangle Summary into showing something that makes sense (and looks nice) for a user when you are working on a form with more complex Group and nested structures.

In this issue we should look into the usage of Summary today, talk to service owners, and design and implement a better Summary that could replace the one we have now. That should, at a minimum, include:

• Smarter and better defaults. We should test against real apps and verify that summaries we generate makes sense and looks nice.
• Recursivity by default. It should be possible to point to either a single component/group or an entire page in the app.
• It should be possible to use a single Summary component to make a summary of the entire current process step, without specifying every component ID you want to summarize.
• It should be possible to point a Summary component to a previous process step. App-frontend could fetch the layouts and data model for that step, and render a summary of the data in it, if you have permissions to read that data.
• Overrides should be configured per-child, not for the entire Summary at once. Take inspiration from tableColumns in repeating Group. It should be possible to render the entire process step summary while at the same time making sure one component deep inside the structure is hidden or hides the 'change' button/bottom border/etc.

This should be a breaking change in the future, but could also be developed alongside non-breaking functionality (either by using feature flags or by implementing a new Summary2 component meant to replace the older one in a future major version).

PDF related issues

Beta Give feedback

1. Option to add a watermark on the generated PDF receipts app-lib-dotnet#787
   kind/user-story +1
   
2. Cypress tests for new PDF generator #865
   area/summary area/test +2
   
3. Ability to preview the PDF before submitting the form #1804
   area/summary kind/user-story +2
   
4. Ability to mark preview generated PDF's with "not valid" #1805
   area/summary kind/user-story status/draft +3
5. Service owners logo should follow the same as for regular pages #1808
   area/summary ux +2
   
6. Font size needs to be scaled down in PDF #2401
   area/summary ux +2
   
7. Timestamp on pdf-print missing #1589
   kind/feature-request org/krt +2
   
8. MapComponent - PDF presentation #2044
   kind/bug +1
   
9. Pagebreak for PDF happens in the middle of components #2480
   kind/bug +1
   
10. Make new summary rendring work with pdf work when rendring previous tasks #2191
    area/summary +1
    
11. Make uploaded files visible when rendring summary of previous task #2192
    area/summary +1
    
12. Support servicetask in application process app-lib-dotnet#368
    kind/user-story +1
    

Summary related issues

Beta Give feedback

1. Document Summary2 #2311
   status/triage +1
   

   
2. Text not formatting properly on error message on summary #1655
   kind/bug +1
   
3. Toggle for å automatisk skjule tomme rader i oppsummeringselement #2471
   kind/feature-request org/brg status/triage +3
   
4. Nested group components in summary page #1677
   kind/feature-request ux +2
   
5. Error summary links are wrong when used with the address component #366
   area/accessibility area/summary kind/bug status/triage +4
   
6. Summary2: Ability to disable components not answered #2189
   status/triage +1
   
7. Moving the Edit/endre-button in the compact summary view #1641
   area/summary kind/feature-request status/triage +3
   
8. Upgrade our check answer/summary component #111
   area/summary kind/user-story status/draft status/triage ux +5
   
9. Mulighet til å bestemme tekst på tomt Summary-komponent #2005
   area/summary kind/feature-request +2
   
10. Hidden rows are shown as empty boxes in summary #1553
    kind/bug +1
    
11. Define how groups and repeating groups should handle titles #820
    area/table fe-v4 kind/user-story org/pat ux +5
    
12. Egendefinert tekst på "Tilbake til oppsummering" knappen #1666
    area/summary kind/feature-request org/ssb +3
    
13. Tilgang på neste-side-knapp selv om man kommer fra summary #1515
    area/summary kind/feature-request org/ssb +3
    
14. Format text for PDF component #1570
    kind/feature-request ux +2
    
15. Table summary for RepeatingGroup component #2188
    status/triage +1
16. Preserve line breaks in TextArea on Summary and Pdf #1590
    kind/feature-request org/dsb status/triage +3
    
17. Nested repeating group is not visible when largeGroup=false #834
    area/accessibility area/summary kind/bug org/brg org/krt org/ssb ux +7
18. In repeating group when setting the mode to "onlyTable" it hides the other datamodels from the summary component #1703
    kind/bug org/ssb +2
    

Component list

Beta Give feedback

1. PDF - Header #2055
   area/summary +1
   
2. Subform: handle targeting current task to create a summary of the main form and all the subforms #2414
   status/triage +1
   
3. Subform: handle targeting a subform layoutset using summary2 to create a summary of the subform #2413
   8 of 8
   area/summary +1
   
4. Payment #2389
   +0
   
5. Map #2387
   +0
   
6. Tabs #2390
   +0
   
7. Compact summary for Grid component #1265
   area/summary kind/feature-request org/dibk org/krt org/ssb status/triage ux +7
   
8. Tests for all components #2367
   area/summary +1
   
9. Grid (table) #2049
   area/summary org/krt +2
   
10. Address #2050
    area/summary +1
    
11. File upload with tag #2051
    area/summary +1
    
12. File upload #2058
    area/summary +1
    
13. Repeating groups #2052
    area/summary +1
    
14. Grid (layout) #2053
    area/summary +1
    
15. Radio group #2060
    area/summary +1
    
16. Checkbox group #2061
    area/summary +1
    
17. Group #2062
    area/summary +1
    
18. Page #2063
    area/summary +1
    
19. Input #2087
    area/summary +1
    
20. Text Area #2174
    area/summary +1
    
21. Dropdown #2184
    area/summary status/triage +2
    
22. MultipleSelect #2185
    area/summary status/triage +2
    
23. List #2388
    +0
    
24. Likert #2386
    area/summary +1
    

Summary2 component tasks

Beta Give feedback

1. Create Summary2 component #2070
   area/summary +1
   

   
2. Docs: remove layoutSetID
3. Docs: explain overrding components on a page
4. Docs: update isCompact explanation

[xmrsa]

I have added a relevant issue to this, regarding the placement of the "Endre"/"Change"-button in the layout of summaries of Group-components. #1641

[madsenandreas]

Situation:
A component of type "Summary" linked by "componentRef" to a "Group" component displays "Du har ikkje lagt inn informasjon her" to a subcomponent in the group even if the user have not used the component which can confuse the person filling the form out.

Wished Situation
Components not used in a group will not be displayed in the summary component.

My Case
In my case the group has dynamics which shows different components depending on prior choices in the group. The picture below has one component "Fag" with choices "Ingen", Grunnleggende..." this is optional to fill out. It also has a component "Matematikk deltakelse" this is also optional. The applicant can attend both or just one of these. The issue arises when just one of these is selected then the second one in summary gets the text "Du har ikkje lagt inn informasjon her".

How the summary component will look like:

[olemartinorg]

Relevant discussion:

• https://altinn.slack.com/archives/C02EJ9HKQA3/p1706876059347139