dataaccepttype Do we need to consider this parameter in our NCMP internal Java interface?
2
datacontenttype Do we need to consider this parameter in our NCMP internal Java interface?
3
attributes This has plural but all examples contain a single String, why?
4
The study mentions 'fields and attributes". None of the examples use 'fields'. We can see only 'value' Objects (in the write use cases)
5
Combine all java api paramaters into 1 parameter object
There is a limit (sonar quality check) of 7 parameter max for a method
Team follow common practice and have a few parameters ie. dataJobId is NOT part of the client request but generated in DCM so it seems logical to keep this separates
The order of Operations is important and needs to be maintained hence the use of 'List'
The output is 'void' for the scope in this user story, it will be defined later
dataaccepttype and datacontenttype might be needed too, see issue #1 and #2. If required we could combine them to reduce the number of parameter in an object like RestProtocolParameters
Proposed structure for Operation
Name
Description
Type
path
It is a unique identifier of a managed object (MO) on a network element. Defines the resource on which operation is executed. Typically could be Fully Distinguished Name (FDN).
String
op
Describes the operation to execute. The value can be:
"add", "replace", "remove", "action", "read"
String
operationId
Unique identifier of the operation within the request
Integer
attributes
Allows selection of specific fields for attributes with complex data type for the operation.
List of String
value
It is for only WRITE operation.
Object
scopeType
ScopeType selects MOs depending on relationships with Base Managed Object. Only for READ operation.
String
scopeLevel
Only for READ operation. Only used once the scope type when BASE_NTH_LEVEL.
Integer
filter
The parameter is used to filter the scoped Managed Objects. Only Managed Objects passing the filter criteria will be fetched.