Hi Koen,
We're interested in this work too.
For now we'll need to use the generic JSON construct with conten-type "application/json-patch-query+json" assuming our async processing will be successful for:
- 1. update note
- 2. update contact info
- 3. update appointment slot
The path expression like for instance
//relatedParty[role='TechnicalContact']/contactMedium[mediumType='email']/characteristic/emailAddress
can't really be checked with the swagger but if we don't find the content it will be an error.
This would result in a collection of "op", "path", "value" objects.
For use cases 1 & 2 one could assume a sync confirmation is quickly possible, for 3 - depending on your business logic it probably needs more complex processing.
In our case 1,2 & 3 have an async workflow behind it.. so ideally an async way of working rather....
We'll update the temporary solution when the async amend specifications would become available.
------------------------------
Peter Broucke
Proximus SA
------------------------------
Original Message:
Sent: Nov 18, 2024 04:28
From: Koen Peeters
Subject: TMF622 - Amend Product Order (in-flight) - Missing State Lifecycle and event flows/mechanisms + How via patch 'using application' json?
The wholesale broadband Workgroup is currently evaluating a proposal from the FIT workgroup in Germany that has identified several amend productOrder use cases and created proposals for 2 or 3 different Amend Tasks.
Some of the identified use cases include:
- changing ProductOffering (upgrade/downgrade)
- changing Appointment (impacting ProductOrder orchestration)
- changing Resources (e.g. new phonenumber instead of porting)
The complexity of these use cases make a synchronous PATCH not feasible.
Let's allign on the content of the Jira request to cover this detail.
Regards
------------------------------
Koen Peeters
OryxGateway FZ LLC
------------------------------
Original Message:
Sent: Nov 18, 2024 03:32
From: Peter Broucke
Subject: TMF622 - Amend Product Order (in-flight) - Missing State Lifecycle and event flows/mechanisms + How via patch 'using application' json?
It looks to me indeed like a good idea to have such JIRA for a future version of the specification with this.
Thanks.
------------------------------
Peter Broucke
Proximus SA
Original Message:
Sent: Oct 23, 2024 09:19
From: Olivier Arnaud
Subject: TMF622 - Amend Product Order (in-flight) - Missing State Lifecycle and event flows/mechanisms + How via patch 'using application' json?
Hi
I understand that one of the need would be to have a task (REST resource) like /amendProductOrder and the accordingly states. Why not, I write a JIRA for future version of the specification, with also the idea to have a /submitProductOrder.
Patch with application/json is described in v5 (I see it in the OAS).
Yes you can update several attributes at same time with a PATCH application/json, but not several resources (to my knowledge).
For me the event is not an answer to a request, so the API client must subscribe to the event, then it will receive the event when for instance the state will have changed, but it may have no relationship with a request.
------------------------------
Olivier Arnaud
Orange
Original Message:
Sent: Oct 21, 2024 14:31
From: Rakshit Simha
Subject: TMF622 - Amend Product Order (in-flight) - Missing State Lifecycle and event flows/mechanisms + How via patch 'using application' json?
It depends if you require a state publishing / tracking mechanism for the amend request itself - if you do not, then a PATCH on the product order will result in a synchronous response showing success or failure. But if you have more complex state transitions, you can look at the Task Resource pattern in TMF630. The CancelProductOrder in TMF622 is a realization of this pattern. You can use the Task Resource pattern to create a shepherd for your order amendment.
---
------------------------------
Rakshit Simha
Oracle Corporation