I'm interested in a discussion on the finer points of "change" product orders, specifically characteristic changes.
In the TMF 622 user guide there are sample payloads that indicate that only the "change" is sent downstream (along with bundle order items with an action code of "noChange")
Additionally important to the discussion is that in the 622 swagger, characteristics don't carry action codes.
In a scenario where a characteristic is added or the value changed the user guide reco and swagger seem to work. The line item carrying the characteristic has an action code "modify" and the new characteristic is provided, or the same characteristic is provided with updated value.
However, what happens when a characteristic is removed as part of the change - how is that communicated?
------------------------------
Lynn Dueck
Oracle Corporation
------------------------------