Survey Response Summary

The Responses blade was a table of raw responses, one column per question (survey response management). Seeing what the responses say — how many picked each option, the average rating — meant building a Dashboard over the survey's dataset. Google Forms answers it on the response page itself: a Summary tab of one chart per question beside the Individual view.

How it works

The blade is a UiTabs pair, Summary (the default) and Individual, which is the table and detail dialog as they were. Summary is a column of cards, one per question in the survey's own order, each drawn by getSurveySummaryCards from what kind of question it is:

Each card is headed by the question's title and "n responses", counting the responses that answered it, so a skipped optional question reads honestly.

• No new procedure. The blade reads the survey's content beside its response records, both existing owner reads, and parses the model with survey-core's Model, as the respondent page does — so a question's kind, its title and its choices' labels (a boolean's Yes and No, a rating's scale) are SurveyJS's own. Choices are shown by their labels rather than their stored values. Only questions the records hold a column for are summarised, so presentation elements have no card. The two reads fail apart: a survey that cannot be read shows its error in the Summary alone, and the Individual view still lists the responses.
• Charts are the dashboard's engine. The bars are StyledApexChart's horizontal bar chart, themed as every chart in the app is; no chart dependency is added.
• The row cap applies as everywhere. A survey past it shows the truncation alert above both views (dataset row-cap warning), since the summary is computed from what was read.
• Before the first response the Summary view is the same empty state the table shows.

flowchart LR
  READ["survey.readSurveyResponseRecords"] --> REC[records]
  CONTENT["survey.readResourceContent"] -->|"survey-core Model"| Q[kind · title · choices]
  REC --> AGG{getSurveySummaryCards}
  Q --> AGG
  AGG -->|choice, rating| BAR[count per choice → bar chart]
  AGG -->|number| STAT[minimum · average · maximum]
  AGG -->|other| LIST[answers]

What is deliberately not in it

• Not SurveyJS Dashboard. It is SurveyJS's proprietary analytics component, licensed per developer; the card kinds above cover what Google Forms' summary shows with code already owned.
• No "latest" answers. A response is stored under a random key with no submission time a list could order by, so a written question's card lists the first answers read and sends the reader to the Individual view for all of them.
• No cross-filtering ("only respondents who answered Yes"). That is the Dashboard's job, and the survey is already a dataset it binds to.
• No per-question view (Google Forms' Question tab). The Individual table sorts and searches by column, which is the same lookup.

Key files

Sources

• Google Forms Help — view and manage form responses — the Summary tab of charts per question beside the Individual tab.
• SurveyJS licensing — the Form Library is MIT while Dashboard is proprietary, which is why the summary is built on the app's own charts.