Bug #3056
Session Failed Report Testing Issues
Description
During testing of the Session Failed Report, the following UI improvements and data changes are required:
1. Correct icons for report sections
Update the icons for the following sections so users can understand the purpose of each section immediately from the icon itself:
Top Errors – use a warning/error-related icon.
Unique Failed Users – retain the current users-related icon.
Car Model Wise – use a car/vehicle icon.
Capacity Wise Session Failed – use a battery/energy capacity-related icon.
Failed Rate — Last 7 Years – use a trend/chart/analytics icon.
Type Wise – use an appropriate session/type/category icon.
The icons should be clear, intuitive, consistent, and visually aligned with the section title.
2. Maintain consistent typography and UI styling
For all the above sections, keep the same font family, font size, font weight, spacing, row height, header styling, alignment, badges, and overall presentation as currently used in the Unique Failed Users table.
Do not introduce different typography or table styling between sections.
3. Add Error Code in the failed-session details table
In the detailed failed-session table, add an Error Code column immediately after the Charger Name column so the sequence is:
Charger Name → Error Code → other existing columns
The error code should be displayed clearly for each failed session and should follow the same font and formatting style as the existing table data.
4. Expected Result
The Session Failed Report should have a consistent visual hierarchy across all sections, intuitive icons that make each section easily understandable, and the detailed failed-session table should show the Error Code directly after the Charger Name.
Updated by Yashaditya Singh about 2 months ago
focused on refining the EV Charging Management System's frontend components. Initially, we resolved an overflow issue in the CompanyDomainModal by adjusting the TableContainer styling to ensure all registered domains are fully accessible via scrolling. The primary focus then shifted to the SessionFailedReport component. We successfully integrated a new errorDetails data structure, replacing the legacy single-string error format. I implemented a robust helper function to parse multiple OCPP error codes—such as info, status, and vendorErrorCode—and render them dynamically as distinct, color-coded UI chips. Finally, we aligned the table headers across all four drill-down drawers to perfectly match the new data columns, ensuring a polished and intuitive user experience.