US-EPA-CAMD / easey-ui

Project Management repo for EPA Clean Air Markets Division (CAMD) Business Suite of applications
MIT License
0 stars 0 forks source link

Add Force Re-Evaluation option #6057

Open esaber76 opened 10 months ago

esaber76 commented 10 months ago

On the Evaluate screen, add an option to force re-evaluation of MP, QA, and EM data.

There is a check that requires the evaluation of MP's at least once a calendar year. There will also be times when there are plant/unit changes in CBS that are logged to INVENTORY_STATUS_LOG and subsequently require MP's to be re-evaluated.

Users may not know the MP needs evaluation flag is set but QA/EM evaluations will indicate that the MP needs evaluation.

It would be useful for users to just be able to re-evaluate all affected data using this flag at once.

Have also come across instances in 2.0 testing where QA and EM evaluations indicate the MP needs to be evaluated even though the MP status is Passed, Updated on Host, and the Monitoring Plan cannot be selected for evaluation. The user either needs to make a temporary change to the MP or export/re-import the MP to trigger the evaluation.

annalbrecht commented 8 months ago

Users should have the option to force a re-evaluation of their data.

This will require a new button, and the check engine will be called for the data indicated.

ergjustin commented 5 months ago

ECMPS 1.0 Evaluation Screen for reference

Image

lgiannini1 commented 5 months ago

Verified on dev using ORIS 50368, CT1

I did notice one issue with force-reevaluations on TEE and EM records. When the user selects a Facility, Location, Reporting Period, clicks Apply Filter, and then checks off the Force-Reevaluation box, previously evaluated TEE and EM records cannot be selected. The user will have to click Apply Filter again before selecting them.

The checkboxes for these records are greyed out after select 50368, CT1, clicking Apply Filter, and then clicking the Force-Reevaluation checbox. Image

After clicking Apply Filter again. Image

lgiannini1 commented 4 months ago

Issue noted above has been resolved on dev.

ntknguyen commented 3 months ago

I verified this option is working.