Santtu Pajukanta

# Further improvement Allow changing this until the first response has been sent.

See also #402

While the `Dimension` and `DimensionValue` models are already unified across Program V2 and Surveys V2, so far they have used their own GraphQL APIs. This combines GraphQL query types and...

Generalize the dimension editor implementation so that it is not directly tied to Surveys V2, then employ it for Program V2

For one or all program forms? Single program form notifications can be handled by the existing survey response subscription facility, but we currently have no way of saying "if new...

Apply an equivalent of `DimensionFilterInput.filter(survey.responses.all(), filters)` on the `responses` being exported.

Make new entry types for this such as `forms.response.viewed` and `forms.response.exported`. If fields from `Person` are exported, should additionally log `core.person.exported`.

The key field support already exists, but there's no facility to mark fields as key fields. Should probably hoist the key fields from being a property on a field to...

Separating these from SingleSelect, MultiSelect and RadioMatrix so that they are easier to support in the form editor. The DimensionRadioMatrix is NICETOHAVE. Perhaps offer the option of having the dimension...