Open APIs

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
------------------------------

Perhaps the answer is that the product modelling accounts for this scenario?
If a product specification has multiple characteristics, if there is any way they can be "removed" then should they be modelled as booleans that can be turned on/off?

------------------------------
Lynn Dueck
Oracle Corporation
------------------------------

Original Message:
Sent: Jun 11, 2021 11:46
From: Lynn Dueck
Subject: Characteristic changes on product order

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
------------------------------

Hello Lynn

This is a fair question, and probably several patterns with or without extension could be envisaged.
I tend to think that order is intend based - in particular for characteristic, relationship and link to place: describe in the product order the "wanted" product representation (a future vision of your product as you want it to have in the inventory). Because of this, we should not pass 'ordering' attribute but only keep the inventory representation. Consequently, it requires that you pass in the order all the product characteristic (and relationship) and it's up to the back end to compare former/wished product configuration and trigger appropriate delivery process(es).

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Jun 11, 2021 12:11
From: Lynn Dueck
Subject: Characteristic changes on product order

Perhaps the answer is that the product modelling accounts for this scenario?
If a product specification has multiple characteristics, if there is any way they can be "removed" then should they be modelled as booleans that can be turned on/off?

------------------------------
Lynn Dueck
Oracle Corporation

Original Message:
Sent: Jun 11, 2021 11:46
From: Lynn Dueck
Subject: Characteristic changes on product order

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
------------------------------