Export History List
Component Detail
Description
Displays the audit log of past Bufdir exports for the current organisation, showing who triggered each export, the period covered, format, and download link. Supports compliance and re-download scenarios.
bufdir-export-history-list
Summaries
The Export History List delivers immediate compliance and operational value by giving authorised staff a transparent, auditable record of every Bufdir export ever generated by their organisation. When auditors or management request evidence of past submissions, staff can locate and re-download any previously generated file in seconds rather than contacting IT support or searching shared drives. This reduces administrative overhead, supports regulatory audit trail requirements, and eliminates the business risk of lost or unverifiable export records. As a shared component reused across multiple reporting contexts, it also avoids duplicate development investment while ensuring consistent audit log presentation across the entire platform.
The Export History List is a medium-complexity shared frontend component backed by the `bufdir_export_audit_log` data model. Development scope includes paginated list rendering, metadata display columns (triggered by, timestamp, period, format, status), re-download action handling, and period-range filtering. Its shared component status is the primary project risk: any interface changes affect all consuming features simultaneously, requiring cross-team coordination before modifications. The upstream export history API endpoint must be ready before frontend integration can begin — flag this as a dependency in sprint planning.
QA coverage must include pagination edge cases, empty-state rendering when no history exists, and re-download failure scenarios. Budget one to two additional days for cross-team regression testing due to the shared component nature.
The Export History List is a shared frontend component deployed in both web and mobile execution contexts, consuming the `bufdir_export_audit_log` data model. It exposes five interfaces: `loadExportHistory(organisationId)` to fetch paginated records from the API, `onRedownload(exportId)` and `onViewDetails(exportId)` as action callbacks, `refreshHistory()` for manual cache invalidation, and `filterByPeriod(DateRange)` for period-scoped filtering (implement server-side for large datasets). Because this is a shared component, its prop and callback interfaces must remain stable — use a well-typed `ExportRecord` DTO and enforce a deprecation cycle before making breaking changes. The re-download action must handle asynchronous file generation states (pending, ready, error) with appropriate loading indicators.
Mobile layout requires responsive column collapsing: prioritise date, status, and action columns on small screens.
Responsibilities
- Render paginated list of past export records
- Allow re-download of previously generated export files
- Display metadata: triggered by, timestamp, period, format, status
Interfaces
loadExportHistory(String organisationId)
onRedownload(String exportId)
onViewDetails(String exportId)
refreshHistory()
filterByPeriod(DateRange range)
Related Data Entities (2)
Data entities managed by this component