-
Story
-
Resolution: Done
-
Medium
-
None
Should report cm handles that have unacceptable alternate ids during registration: create.
- duplicated in the batch request
- already in the database for another cm handle.
The current error reporting format:
{ "failedCreatedCmHandles": [ "cmHandle": "ch 1", "errorCode": "109","errorText": "cm-handle already exists"}], "failedUpdatedCmHandles": [], "failedRemovedCmHandles": [], "failedUpgradeCmHandles": [] }
Error Scenarios
Scenario | Report | Notes | |
---|---|---|---|
2 | Used for other cm handle in the database | 111, Alternate id already associated | Part of 'failedCreatedCmHandles' |
3 | Used for other cm handle in the request | 111, Alternate id already associated | Part of 'failedCreatedCmHandles' |
Out of scope:
- Invalid Alternate Ids themselves are not part of error response
A/C
- Both error scenarios shall be tested and demo-ed
- new error code (111) should be included in the RTD