Varun
There is no magic here. Handling multiple in-progress pending orders is not easy, which is why it is not simple to create robust commerce and ordering solutions for the telco industry.
The API signatures are just that, signatures. Behind the signatures a lot of software design and development work is needed to get the correct results. Just consider one example:
- On 2-April-2024 Customer requests a Move (change address) order for their broadband. The requested date is 2-June-2024. Since the target address does not have fiber, the move order includes also a downgrade of bandwidth from 500 Mbps to 200 Mbps
- On 10-April-2024 Customer requests a configuration change, adding a security feature Firewall to the broadband. The requested date is 10-April-2024
You will note that the pending move order will have embedded product configuration that does not include the Firewall feature. So if executed as-is, the customer will lose the Firewall. The software will need, perhaps, to make adjustment to the product configuration in the move order.
This has nothing to do with the API signature.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Jun 03, 2024 15:03
From: Varun Pandhi
Subject: Changes to Product in context of ProductOrder
Hi Jonathan,
Thanks for the response.
Even if we take the decision to not update the Product Inventory till the Change Order is not yet completed (or reached point of no return).
Still after Change Order is completed, if we issue a GET of New Provide order, it would exhibit the Product information related to Change Order (Thus leading to loss of Product state during New Provide order).
How does TMF 622 Open API handle this?
------------------------------
Varun Pandhi
Infosys
Original Message:
Sent: Jun 03, 2024 07:42
From: Jonathan Goldberg
Subject: Changes to Product in context of ProductOrder
Hi Varun
The inventory APIs, including Product Inventory, do not currently exhibit versioning behavior.
Therefore, for non-Provide (MACD) orders, you probably won't want to update the inventory until the order is completed (or at least has reached the point-of-no-return).
I imagine that if and when the ODA use cases start to deal with non-provide orders we will see where they recommend to update the inventory. Until that time, the "new" product (or service, or resource) will be embedded within the order.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Jun 03, 2024 02:05
From: Varun Pandhi
Subject: Changes to Product in context of ProductOrder
Hi all,
While going through API documentation for TMF 622 Product Order. When changes occur on a Product in context of Product Order, same instance of Product gets changed. Post this, if someone does a GET Product Order for New Provide, they will not see the Product instance at that point of time when New Provide order was placed.
Lets take an example for a New Provide order with below instance model -
For change order scenario, we could have below instance model -
Now, if we try to do GET Product Order for P1 (New Provide Order), since values of Product Characteristic with respect to Flavour have changed to Advanced, it will show the same in context of New Provide order as well, which is not correct.
Is there any version management in Product resource or how is this scenario handled wherein each Product Order should only provide values for attributes for Product resource that are relevant to ProductOrder and values for ProductCharacteristic that are relevant to ProductOrder?
------------------------------
Varun Pandhi
Infosys
------------------------------