Open APIs

 View Only
  • 1.  TMF 641 - clarification around expectedCompletionDate

    TM Forum Member
    Posted Sep 28, 2020 22:07
    Edited by Rati Mehrotra Sep 29, 2020 02:11
    Hi All,

    641 has an attribute expectedCompletionDate and completionDate. The definition says

    expectedCompletionDate

    A date time (DateTime). Expected delivery date amended by the provider.


    completionDate

    A date time (DateTime). Effective delivery date amended by the provider.


    and it is also marked as a PATCHable attribute in the document.

    Wanted to understand how can consumer patch it when it is the expected date from provider.  Or does PATCHable attribute mean that it can be modified by provider and consumers both ?

    Thanks,
    Rati
    @Uma Lakshman

    ------------------------------
    Rati Mehrotra
    Telstra Corporation
    ------------------------------​


  • 2.  RE: TMF 641 - clarification around expectedCompletionDate

    TM Forum Member
    Posted Sep 29, 2020 02:23
    Hi Rati

    The Open API definitions do not deal with consumer authorization. The assumption is that there is authorization control applied externally (e.g. in an API gateway) so that only allowed roles can invoke an API operation. This could be made more fine-grained, to attribute level, depending on the capabilities you have in your control system.

    Specifically for this example, we could imagine (perhaps) that a Service Order might be exposed to engineering staff by some internal UI, and these people might need to update the dates according to actual progress in the order. Even though the original submitter of the service order would probably not be able to update the dates.

    But adding @Ludovic Robert to comment as well.

    Hope it helps​

    ------------------------------
    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: TMF 641 - clarification around expectedCompletionDate

    TM Forum Member
    Posted 8 days ago

    I am referring the document TMF641_Service_Ordering_Management_API_User_Guide_v4.1.0.pdf. As per this document, cancellationReason, completionDate, & CanellationDate are marked as non patchable attribute.

    Could you please suggest, how to update these dates?



    ------------------------------
    PANDIAN Ramakrishnan
    Infosys
    ------------------------------



  • 4.  RE: TMF 641 - clarification around expectedCompletionDate

    Posted 7 days ago
    I am a bit confused by the question. These dates are updates in the system of record by the provider of the service who is fulfilling the order. Their purpose is to inform the customer as to the expected and actual completion date for the order. They are not intended for the customer to dictate the target date of the order or state when they think the service was delivered.