Open APIs

Hi

As per the TMF641 Spec

As per the state model, Cancelled state is the final state of the Order & there is no transition from Cancelled state for the Order.
In short, the Order has been deleted/removed.


Is Cancelled state equivalent to ServiceOrderRemoveNotification? & one notification is sufficient OR
Secondly, we send out 2 notification; one ServiceOrderStateChangeNotification with state=cancelled & second should be sent out for ServiceOrderRemoveNotification too?

Wanted to understand which approach makes sense? & Why?

 

Thanks

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

This is a very good question, and would apply also to other entities that have end-states like canceled (e.g. Product Order, Resource Order, Shopping Cart, etc.). I suggest to raise with the API chief architect @pierre gauthier for guidance as to which events to raise in this situation.​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------

Original Message:
Sent: Oct 06, 2018 03:53
From: Vikas Kumar
Subject: 641: Order Cancelled State & RemoveNotification

Hi

As per the TMF641 Spec

The Cancelled state is where an In-Flight Order has been successfully cancelled.

As per the state model, Cancelled state is the final state of the Order & there is no transition from Cancelled state for the Order.
In short, the Order has been deleted/removed.


Is Cancelled state equivalent to ServiceOrderRemoveNotification? & one notification is sufficient OR
Secondly, we send out 2 notification; one ServiceOrderStateChangeNotification with state=cancelled & second should be sent out for ServiceOrderRemoveNotification too?

Wanted to understand which approach makes sense? & Why?



Thanks

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

Hello

Yes that a good question.
I'm wondering if we should not simply remove the 'ServiceOrderRemoveNotification'  because we never really remove it except.. when we clean the DB long time after the serviceOrder was in a final state (and at this time I'm supposing nobody care).
State change notification should be enough.

Ludovic

------------------------------
Ludovic Robert
Orange
------------------------------

Original Message:
Sent: Oct 10, 2018 02:26
From: Jonathan Goldberg
Subject: 641: Order Cancelled State & RemoveNotification

This is a very good question, and would apply also to other entities that have end-states like canceled (e.g. Product Order, Resource Order, Shopping Cart, etc.). I suggest to raise with the API chief architect @pierre gauthier for guidance as to which events to raise in this situation.​

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Oct 06, 2018 03:53
From: Vikas Kumar
Subject: 641: Order Cancelled State & RemoveNotification

Hi

As per the TMF641 Spec

The Cancelled state is where an In-Flight Order has been successfully cancelled.

As per the state model, Cancelled state is the final state of the Order & there is no transition from Cancelled state for the Order.
In short, the Order has been deleted/removed.


Is Cancelled state equivalent to ServiceOrderRemoveNotification? & one notification is sufficient OR
Secondly, we send out 2 notification; one ServiceOrderStateChangeNotification with state=cancelled & second should be sent out for ServiceOrderRemoveNotification too?

Wanted to understand which approach makes sense? & Why?



Thanks

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------