Updates for already submitted TEE's

[esaber76]

Users have the ability to remove and/or modify already submitted TEE's from their workspace. This could impact emissions evaluations. TEE's that need to be modified and/or removed should first be handled in the Admin tool.

• Remove the ability to delete already submitted TEE's from the workspace.
• For already submitted TEE's, the extension/exemption type, system ID, component ID, and fuel code fields should be read-only at a minimum (similar to 1.0).
• For a new TEE that has been saved but not submitted in 1.0, the same fields are set to read-only on save. This may not need to necessarily happen in 2.0 so long as changing these fields requires a re-evaluation of the TEE and any dependent data.

[yonatan-dp]

Hi @esaber76 , for this ticket, I am assuming we will use the same acceptance criteria as in #6061 except that we are using camdecmpswks.test_extension_exemption and the camdecmps.test_extension_exemption tables with test_extension_exemption_id column as the identifier.

[esaber76]

@yonatan-dp - yes.

[lgiannini1]

Verified that previously submitted TEEs cannot be removed from the workspace. There are some issues though:

• The Extension or Exemption Code field for previously submitted TEEs is editable instead of read-only.
• When attempting to add a new TEE record, the Monitoring System ID, Component ID, and Fuel Code fields are all read-only which prevents users from saving the record.

[yonatan-dp]

@lgiannini1 Please retest, fix deployed to Dev.

[lgiannini1]

Verified on dev.

• Check out ORIS 147, K-7
• Verify that there is no "Remove" button for previously submitted TEEs
• Click the "Edit" button on a previously submitted TEE and verify that the extension/exemption type, system ID, component ID, and fuel code fields are read only
• Add a new TEE for Component with Extension or Extemption Code RANGENU
• Click the "Edit button on the newly created QA Cert Event and verify that the extension/exemption type, system ID, component ID, and fuel code fields are read only
• Verify that the newly created QA Cert Event can be removed from the workspace.
• Add a new QA Cert Event, submit it, and verify there is no "Remove" button for the event after submission

[ntknguyen]

1. Cannot verify

• no "Remove" button for previously submitted TEEs. (image)

2. Verified:

• The extension/exemption type, system ID, component ID, and fuel code fields are read only in both QA Cert Event and TEE.
• Newly QA Cert Event can be removed from the workspace.
• Added new TEE
• "Remove" not showing up next to the newly QA Cert Event after submission.

[yonatan-dp]

@ntknguyen, I looked into this. The TEE data for Kyrene Generating Station, K-7 was not submitted. I verified this by checking in the database that it only existed in the camdecmpswks.test_extension_exemption table (it was not in the official record: camdecmps.test_extension_exemption). That is why you were able to see the "Remove" button. I run the following two queries to determine that:

--This returns one TEE data select * from camdecmpswks.test_extension_exemption tee where tee.mon_loc_id = '3914';

--This returns empty TEE data select * from camdecmps.test_extension_exemption tee where tee.mon_loc_id = '3914';

Just to make sure, I went ahead and "Reverted to Official" and the TEE data you screenshot disappeared (as it should since reverting to official will revert to the official data from the camdecmps schema).

I conclude from the above that the functionality is working as intended. Please let me know if I missed something in my analysis above.

[ntknguyen]

@ntknguyen, I looked into this. The TEE data for Kyrene Generating Station, K-7 was not submitted. I verified this by checking in the database that it only existed in the camdecmpswks.test_extension_exemption table (it was not in the official record: camdecmps.test_extension_exemption). That is why you were able to see the "Remove" button. I run the following two queries to determine that:

--This returns one TEE data select * from camdecmpswks.test_extension_exemption tee where tee.mon_loc_id = '3914';

--This returns empty TEE data select * from camdecmps.test_extension_exemption tee where tee.mon_loc_id = '3914';

Just to make sure, I went ahead and "Reverted to Official" and the TEE data you screenshot disappeared (as it should since reverting to official will revert to the official data from the camdecmps schema).

I conclude from the above that the functionality is working as intended. Please let me know if I missed something in my analysis above.

Thanks @yonatan-dp. The issue is now fixed.