Table content of parts view can be downloaded as CSV format file.

[rogocof]

As a user (or supervisor),
I want to export the parts list—with the current filters and column configuration—into a CSV file
so that I can efficiently export only the data that is relevant to my needs.

Hints / Details

- Export Button Availability:

An export icon is available in the parts list view (as per Figma design files).

- CSV Generation on Click:

When the user clicks the export button:

The application generates a semicolon-separated CSV file.

The file adheres to the current filter settings applied on the UI table.

The CSV uses the user’s custom column configuration.

Depending on the user’s browser/system settings, the file will be directly downloaded using the generated filename or the file download dialog will show up.

- Data & File Formatting:

All attributes are formatted as strings.

Dates are formatted in the ISO format: YYYY-MM-DDTHH:MM:SSZ (e.g., 2022-02-04T14:48:54Z).

The CSV is encoded in UTF-8.

The first row of the CSV contains the header.

Headers should use the same name as displayed in the UX (important when we use custom translations at a later stage)

- Default File Name:

The exported file will have a default generated filename in the format: YYYY-MM-DD-HH:24:MM_part-list.csv (using the current date and time).

- Error Handling:

If an error occurs during CSV generation, a general error message is displayed to the user.

- Documentation:

The export functionality is documented in the User Manual under “How to export CSV file,” which explains all the available options and defaults in use.

Acceptance Criteria

Feature: CSV Export of Parts List

Scenario: Successful CSV export with complete parts list
Given the parts list is displayed with custom filters applied and a user-configured column configuration
When the user clicks the "Export CSV" icon
Then a semicolon-separated CSV file is generated
And the CSV file is encoded in UTF-8
And the first row of the CSV contains headers using the names displayed in the UX (including any custom translations)
And all attributes are formatted as strings with dates in the "YYYY-MM-DDTHH:MM:SSZ" format
And the file download dialog (or direct download) shows a default filename in the format "YYYY-MM-DD-HH:24:MM_part-list.csv"

Scenario: Successful CSV export when filtered to show only own parts
Given the parts list is displayed with a filter applied to show only own parts
When the user clicks the "Export CSV" icon
Then a semicolon-separated CSV file is generated
And the CSV file is encoded in UTF-8
And the first row of the CSV contains headers using the names displayed in the UX (including any custom translations)
And all attributes are formatted as strings with dates in the "YYYY-MM-DDTHH:MM:SSZ" format
And the file download dialog (or direct download) shows a default filename in the format "YYYY-MM-DD-HH:24:MM_part-list.csv"

Scenario: Handling errors during CSV generation
Given the parts list is displayed
And an error occurs during the CSV generation process
When the user clicks the "Export CSV" icon
Then a general error message is displayed to the user indicating that the export failed

Out of Scope

child relationship