Update Form and Schedule Schemas to match updated specification templates

[GreggMoreland]

Business Reason

Task 1: Update the Form 3X schema to match the current updated specification standards, using the specification in this document

Task 2: Verify the Form 1M schema matches the current updated specification standards, using the specification in this document (Differences highlighed in yellow)

• All Form 1M changes are complete

Task 3: Verify the Form 24 schema matches the current updated specification standards, using the specification in this document (Differences highlighed in yellow)

• All Form 24 changes are complete

Task 4: Verify the Form 99 schema to matches the current updated specification standards, using the specification in this document (Differences highlighed in yellow)

• All Form 99 changes are complete

QA Notes

• BA/Design Quality Checklist complete
• BA's will verify ticket

DEV Notes

• compare with https://fecgov.github.io/fecfile-validate/
• Note: Even though we are including new fields, we know they are not added to the generated *.fec file because there is no COL SEQ #.

Design

null

FECFILE-548

[AureliaKhorsand]

Thanks @GreggMoreland , let's talk through this at our next sync-up

[WiseQA]

No QA review for this tickets as noted in AC BA's verified ticket before moving to QA bucket.

Ticket moved to Stage Ready.

[AureliaKhorsand]

@sasha-dresden and @GreggMoreland - has this actually been reviewed? I'm looking at the schemas and they don't seem to be updated. I might be totally missing something, but they should be matching what is in the linked documents.

[AureliaKhorsand]

@mjtravers and I chatted, and the schedule updates no longer apply based on how we use (or rather, don't use) the schedule schemas. The schedule schemas match the vendorpak, but we validate against transaction and form schemas. Updated ticket to clarify that it's just the Form ones that need updating. @sasha-dresden @GreggMoreland

[GreggMoreland]

@sasha-dresden @mjtravers Here are the things I have found:

• In C1, it has 'X (warerrorning)' in the validation for Lender State. It should be 'X (error)'
• In C2, GUARANTEED AMOUNT has the 'X (error)' in the Rule Reference column but it should be in the Required column

[mjtravers]

@GreggMoreland The C1 and C2 specs have had the 2 issues listed above corrected:

https://fecgov.github.io/fecfile-validate/SchC1_spec.html
https://fecgov.github.io/fecfile-validate/SchC2_spec.html

[GreggMoreland]

@mjtravers @sasha-dresden @AureliaKhorsand It looks good to me now.

[exalate-issue-sync]

Aurelia Khorsand commented: Sprint accepted 6/18/2024 during Sprint Review.