Open APIs

 View Only
  • 1.  TMF641 v4.1 - errorMessage context

    TM Forum Member
    Posted 18 days ago
    Hi,

    I'm wondering about the context of errorMessage - is it required to persist the errorMessage as part of the service order or it can be used just for event purposes (build it when error occurs and attach it to event payload, use it as non-persistent sub-object)?
    In case we don't persist it, we won't have errorMessage in GET serviceOrder response.

    In case we store it, what should happen if the same order receives a new error during later processing steps?
    Should new error be appended to existing errorMessage structure or overwrite the whole errorMessage structure - should GET serviceOrder return only the latest error or complete history of errors?

    Thanks.

    Best regards,
    Goran

    ------------------------------
    Goran Gacesa
    Ericsson Inc.
    ------------------------------


  • 2.  RE: TMF641 v4.1 - errorMessage context

    TM Forum Member
    Posted 21 hours ago
    Hi Goran

    It's an implementation decision whether to persist or not.
    Regarding history of errors, I don't know what to tell you. The top-level service order supports only a single error message, but contained order items can have a list of error messages.

    P.S. this was initially introduced by your Ericsson colleague @Kamal Maghsoudlou, so you might want to consult with him.​

    ------------------------------
    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.
    ------------------------------



  • 3.  RE: TMF641 v4.1 - errorMessage context

    TM Forum Member
    Posted 3 hours ago
    Hi Jonathan,

    thanks for sharing your thoughts, I also understood there's certain amount of freedom to interpret the whole concept.
    It would be good if some of the members can share the actual implementation and what drove them to a specific design and decision.


    ------------------------------
    Goran Gacesa
    Ericsson Inc.
    ------------------------------