- Fix dimension Pareto datasources: PJ_TYPE/PRODUCTLINENAME from DW_MES_CONTAINER, WORKFLOWNAME from DW_MES_LOTWIPHISTORY via WIPTRACKINGGROUPKEYID, EQUIPMENTNAME from LOTREJECTHISTORY only (no WIP fallback), workcenter dimension uses WORKCENTER_GROUP - Add multi-select Pareto click filtering with chip display and detail list integration - Add TOP 20 display scope selector for TYPE/WORKFLOW/機台 dimensions - Pass Pareto selection (dimension + values) through to list/export endpoints - Enable TRACE_WORKER_ENABLED=true by default in start_server.sh and .env.example - Archive reject-history-pareto-datasource-fix and reject-history-pareto-ux-enhancements - Update reject-history-api and reject-history-page specs with new Pareto behaviors Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
reject-history-detail-export-parity Specification
Purpose
TBD - created by archiving change reject-history-pareto-ux-enhancements. Update Purpose after archive.
Requirements
Requirement: Cached reject-history export SHALL support Pareto multi-select filter parity
The cached export endpoint SHALL support Pareto multi-select context so that exported rows match the currently drilled-down detail scope.
Scenario: Apply selected Pareto dimension values
- WHEN export request provides
pareto_dimensionand one or morepareto_values - THEN the backend SHALL apply an OR-match filter against the mapped dimension column
- THEN only rows matching selected values SHALL be exported
Scenario: No Pareto selection keeps existing behavior
- WHEN
pareto_valuesis absent or empty - THEN export SHALL apply no extra Pareto-selected-item filter
- THEN existing supplementary and interactive filters SHALL still apply
Scenario: Invalid Pareto dimension is rejected
- WHEN
pareto_dimensionis not one of supported dimensions - THEN API SHALL return HTTP 400 with descriptive validation error