Page History

...

1. Capture Incoming subscriptionId from the client.
2. Query the existing subscriptions we are tracking using the subscriptionId we got from the Cm Subscription Delete request.
3. Populate the cmSubscriptionCache with the relevant details ( this will be later used to send the response ) using the above query we did.
4. Now check if the details we have are ALL the last subscribers or not.
   1. if all are NOT the last subscribers then we can right away delete it from the DB and send back the response to the client with without sending any request to the DMI.
   2. if we have mixed records then we need to make a call to the DMI for the "last lights out" to get Acceptance from DMI.
5. if DMI accepts it , then whatever we have in the cache can be used to DELETE the rows from the DB ( similar to what we did for create )
6. Once the rows are deleted then we can send back the response to the client .and clear up the cache ( for ACCEPTED/REJECTED )

Subscription Delete Sequence Diagram

...