References
- CPS-2249Getting issue details... STATUS -
Assumptions
Assumption | Notes | Sign-off | |
---|---|---|---|
1 |
| ||
2 | Default Boolean in cases CM not available | ||
3 | Interface uses FDN |
Open Issues
Issue | Notes | Decision | |
---|---|---|---|
1 | Uplift Ericsson source code (need permission) | ||
2 | Implement in REST or Service Layer ? | ||
3 | Scope details e.g create and delete use-cases | ||
4 | Publish public Conflict Interface as part of NCMP ? | ||
5 | Could we make this more generic to suit non-colic-management use i.e. tbac... | ||
6 | Private properties are used to get FDN at the moment, how will this be handled when alternate ID is fully implemented? |
Requirements
Functional
Interface | Requirement | Additional Information | Signoff | |
---|---|---|---|---|
1 | CPS-E-05 | Design (& Publish ?) generic conflict handling interface
| ||
2 | Intercept CM write requests to allow Conflict Handling Check
| |||
3 | Report HTTP Conflict upon failure
| |||
4 |
Error Handling
Scenario | Expected Behavior | Notes | ||
---|---|---|---|---|
1 | ||||
2 |
Characteristics
Parameter | Expectation | Notes | Signoff | |
---|---|---|---|---|
1 | ||||
2 | ||||
3 |
Solution Proposal
Out of Scope
- Batch (bulk) interface methods
- Data job interface