Load Persisted Period Configuration for Recurring Reports
Many organizations submit Bufdir reports on a fixed schedule — quarterly or annually — and always use the same period structure. Storing the organization's preferred period configuration and pre-loading it on the selection screen reduces the steps required for routine submissions. The persisted configuration should be editable by the coordinator, and changes should be saved back so that the next report cycle also benefits. The configuration is stored per organization unit so that different chapters can have independent default periods.
User Story
Acceptance Criteria
- Given the coordinator's organization has a saved period configuration, when the period selection screen opens, then the preset or date range from the saved configuration is pre-selected and the record count banner updates automatically
- Given no prior configuration exists for the organization, when the period selection screen opens, then the most recently used preset is selected, or the current quarter preset is selected as the system default
- Given the coordinator changes the period from the pre-populated default, when they confirm, then an option is presented to save the new selection as the new default for future reports
- Given the coordinator saves a new default period, when the period configuration repository is updated, then the change is scoped to the coordinator's organization unit and does not affect other chapters
Business Value
Coordinators who submit quarterly Bufdir reports must perform this workflow four times per year. Pre-populating the period from saved configuration removes repetitive data entry, reducing the time-to-submission for routine reports and lowering the cognitive burden on coordinators who manage multiple responsibilities across volunteer organizations.
Components
- Period Configuration Repository data
- Period Selection Screen ui
- Period Preset Service service
- Period Selection BLoC infrastructure