Open APIs

( Context :  state attribute that could take one of the 7 values : feasibilityChecked, designed, reserved, inactive, active, suspended, terminated  )

Is the client to a TMF 638 implementation supposed to send the state with its payload ? ( I thought the TMF 638 implementing server is supposed to make teh  correct state transitions depending on what is being done on the service )

However, I see that state is expected to be sent explicitly with the POST ( Mandatory attribute )

But for PUT it is optional.

PATCH also allows for state to be changed by the client.

Is the client responsible for  manually manage teh state ?

( I could not find a conclusive answer from my searches )

--sony

I believe this service/API is called from Service Order Management Component and hence it is fine that the state is updated externally to the service. I feel, Service Inventory could also subscribe to events and updates it's state on it's own in certain circumstances as well.