Committed data modification endpoint - Provide non-existing or malformed system IDs returns `200`

[lindaxiang]

Test case

• Test endpoint: https://submission.ingress.dev.k8s.pcgl.dev-sd4h.ca/api-docs/#/Submission/put_submission_category__categoryId__data
• Parameters:
  • category: 1
  • organization: TEST-CA
  • files: participant.tsv (participant.tsv)

Observation

1. the provided systemId in the tsv file does not exist. e.g, No Submitted data found with systemId 'Z5HYWR4O1N2WR8F7JA3HX'
2. when submitted with the above test case, it returns 200 with the following

{
  "submissionId": 32,
  "status": "PROCESSING",
  "batchErrors": [],
  "inProcessEntities": [
    "participant"
  ]
}

3. when check the submission with submissionId, it returns 200 with the following:

{
  "id": 32,
  "data": {
    "deletes": {},
    "inserts": {},
    "updates": {}
  },
  "dictionary": {
    "name": "prod_pcgl_schema",
    "version": "1.1"
  },
  "dictionaryCategory": {
    "id": 1,
    "name": "TEST-CA"
  },
  "errors": {},
  "organization": "TEST-CA",
  "status": "VALID",
  "createdAt": "2025-10-28T19:51:22.575Z",
  "createdBy": "PCGL100013",
  "updatedAt": "2025-10-28T20:01:56.856Z",
  "updatedBy": "PCGL100013"
}

Not sure if this is the expected behaviour?

Expectation

• Modify step 2 and indicate the systemId is non-existent under "batchErrors". still returns 200
• in step 3, the status should be 'INVALID", still returns 200.

[leoraba]

this PR handles that scenario, resulting with an INVALID submission with the list of errors.

[leoraba]

@lindaxiang
The fix for this error is ready for testing in dev.

It is handled in the following way:

• The PUT /submission/category/{categoryId}/data endpoint receives the .tsv file and creates a new submissionId in a 200 OK response.
• The .tsv records are evaluated in the background process.
• To retrieve the result of the submission use the GET /submission/{submissionId}
• Check for any errors and status properties in the submission response