AH: Implement Data Preview for Facility

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context (wireframes, business rules, etc.)?
[x] Is this traceable to a feature, epic, or PI?

User Story

As a CAMPD custom data download user I want to preview my dataset with facility filter criteria so that I can confirm it contains my desired data

Acceptance Criteria

Given a user has selected filter criteria When they select Preview Data Then the filter criteria is reflected in the results

Given that a user has selected filter criteria for facility When the preview data functionality is displayed Then the system displays a data table containing the data elements below for the selected criteria (limited to the first 100 records) And the data table contains a scroll functionality to show all columns/rows

Given that a user has selected preview data When the functionality is displayed Then the system will display the dataset's total record count

Context

Wireframes

Filter tags and functionality were completed in ticket Restructure Filter Components for Reusability Across All Data Types #1435

Data Preview

Refer to the CAMPD_ DataLabels_AllowanceCompliance file here Trigger: A user has entered, at a minimum, the required parameters, and selected the option to preview data.

For each record that matches the criteria, the system will display in a tabular format:

ACCOUNT_NUMBER ACCOUNT_NAME ORISPL_CODE PRG_CODE VINTAGE_YEAR TOTAL_BLOCK START_BLOCK END_BLOCK STATE EPA_REGION (2 digit number) OWN_DISPLAY ACCOUNT_TYPE

Results will display total record count (Viewing the first 100 of X records) Results are limited to 100 records (Allowance Holdings API is ordered by PRG_CODE > ACCOUNT_NUMER > VINTAGE_YEAR > START_BLOCK ) Results in preview are limited to the first 100 records Results in preview will have a scroll functionality to show all columns/rows Results columns are are sortable in ascending and descending order (alphanumeric order) . Sort is limited to the original 100 results

Testing

Test Case: Tester:

Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

US-EPA-CAMD / easey-ui