NoneType Affected Systems Trigger an Error on the Report Screen

[karendm]

Current Behavior

Currently, an affected system that is added to a finding but not given a name is added as a NoneType object. This causes an error on the Report screen and while trying to access the corresponding Affected System object within the Admin portal.

Expected Behavior

RE should not create an AffectedSystem object unless it is given a name. Error handling on the Report screen and throughout the app should include resilience to NoneType objects so that the app continues to function normally.

Steps to Reproduce

1. Add a Finding
2. On the Create Finding screen, fill in required fields
3. On the Create Finding screen, add an Affected System but do not modify any of the Affected System fields (leave it blank)
4. Save the finding
5. Navigate to the Report screen and/or to the null AffectedSystem object (should be labelled with a - symbol)
6. View the error in the GUI or logs