Audit data validation in FSR submissions to catch nil values throwing errors

[penny-lischer]

Description

We have an issue with data being submitted to the transform code we've rolled out. After fixing the addressLine2, creditorName, and spouseFullName/last issues and adding error logging, there may be others that should be addressed before errors get thrown.

We need to fix these issues so veterans an continue to submit 5655's

In one instance, Andrew was able to verify that the frontend was setting a default string pre 'transform and submit'. Might be good to revisit the old FE implementation and see if they have use cases that we're missing.

Tasks

• Audit the FE to see what fields had default values being set before the logic switch to BE
• Add the default values to BE found in the audit that are missing
• Add unit tests

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required

Acceptance criteria

• no more errors for missing default values

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the "Then" statement in the description

Testing procedure:
If additional testing steps or credentials to perform testing are needed list them here

---

Ticket creation

Ticket requirements

Required to be "Ready"

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Attach to an Epic
• Estimate Points