Skip to main content

Inconsistent validation between Statewide and Local Claim

Bug Reports

During testing for https://cpuccedars.featurebase.app/p/update-cmpa-validation-errors-to-warnings a bug was uncovered.

Steps to reproduce

Roopa tested the CMPA revised rules with SW upload, and the test results were slightly different from PA upload regarding Upload history status and Summary with the test records.

The same test data was used except Claim, Site, Contact, and Program IDs, which were updated with SW IDs.

Comparison SW Upload vs PA Upload

  1. The upload history status is “passed with warnings,” while the PA upload status is “record_ errors.”

  2. I was expecting ClaimIDs SW-2024-test5 and SW-2024-test8 to fail with CMPA_ApplicationID is empty error, but there were no errors.


Files have been emailed to the team.

Select the module in CEDARS
Select user type
Posted by cedars team ·
Status: Completed2 comments

This request was merged into another request

Comments2

  • RoopaReddy_PGE

    •

    Jan 23, 2025

    @cedars team

    Statewide (SW) must be included in my opinion. SW C&S is exempt, and this is covered in the validation rule already.

  • cedars team

    Team•

    Jan 23, 2025

    This ticket is pending if statewide is meant to be exempt as it currently is with this validation:

    Claim.CMPA_ApplicationID is required when Claim.ClaimID does not end with one of (‘Audit’, ‘Placeholder’) and Claim.ClaimType equals ‘Custom’ and Measure.MeasImpactType does not start with ‘Cust-NMEC-Pop’ and Program.ProgramCategory does not equal ‘Energy Savings Assistance’ and Program.ProgramSegment is populated and Program.ProgramSegment does not equal ‘Codes and Standards’.

    This is why there are inconsistencies.