Open APIs

 View Only
Back to discussions
Expand all | Collapse all

TMF641 - Notification types and states mapping

  • 1.  TMF641 - Notification types and states mapping

    Posted May 13, 2020 09:27
    Edited by Shashank Inamdar May 13, 2020 10:44
    Hello,
    I am trying to gain an understanding on the SO APIs - notification types and states.
    Primarily in our implementation, we see usage of the following event types -
    • ServiceOrderCreateNotification
    • ServiceOrderStateChangeNotification
    • ServiceOrderAttributeValueChangeNotification
    What I seem to be missing is the possible Order States each notification type can send? By this I mean, CreateOrder notification wouldn't possibly send the state other than acknowledged or rejected - on these lines, is there anything documented where one can see the notification type to 'possible states' mapping?


    Also, On order validation and acceptance, a sync response with HTTP status 201 is sent by the server. Is this sent once the order state has already moved to acknowledged/rejected or before that? Would there still be a need to send an Async notification of CreateOrder type with the acknowledged/rejected state?

    Thanks
    Shashank

    ------------------------------
    Shashank Inamdar
    Vlocity
    ------------------------------