Details

    • Type: Bug Bug
    • Status: Ready for QA Ready for QA (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: FN
    • Labels:
      None Labels
    • Customer:
      OMAN-Tel

      Description

      I'm tested the CancelOrder API, I alredy created new orders, 4444900281, on both platform, but, I'm getting error while cancelling :

      Howerver, when no task is complted, all tasks are pending, the workorder is cancelled, but with performance issue 13 seconds compared to 4 seconds on the OLD system. See WO 4444900282.

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
      <soapenv:Header/>
      <soapenv:Body>
      <ser:cancelOrder>
      <!-Optional:->
      <woNo>4444900281</woNo>
      <!-Optional:->
      <cancellationCode>SUBR</cancellationCode>
      <!-Optional:->
      <cancellationReason>UBO</cancellationReason>
      </ser:cancelOrder>
      </soapenv:Body>
      </soapenv:Envelope>

      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <soap:Fault>
      <faultcode>soap:Server</faultcode>
      <faultstring>Transaction silently rolled back because it has been marked as rollback-only</faultstring>
      <detail>
      <ns1:NepFault xmlns:ns1="http://server.api.nep.mobinets.com/">
      <errorCode xsi:type="xs:int" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://server.api.nep.mobinets.com/">1</errorCode>
      </ns1:NepFault>
      </detail>
      </soap:Fault>
      </soap:Body>
      </soap:Envelope>

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
      <soapenv:Header/>
      <soapenv:Body>
      <ser:cancelOrder>
      <!-Optional:->
      <woNo>4444900282</woNo>
      <!-Optional:->
      <cancellationCode>SUBR</cancellationCode>
      <!-Optional:->
      <cancellationReason>UBO</cancellationReason>
      </ser:cancelOrder>
      </soapenv:Body>
      </soapenv:Envelope>

      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <ns2:cancelOrderResponse xmlns:ns2="http://server.api.nep.mobinets.com/"/>
      </soap:Body>
      </soap:Envelope>

        Activity

        Hide
        Zein Trabelsi added a comment -

        before lunch the cancel process the app retrieve the process name + usage type + order type from flowable database (same logic in both platform) .
        the reason the performance is better in old is that we made flowable database cleanup in staging and we didnt make it in 84 flowable database .
        3 queries in flowable database in 84 took > 8s .

        Show
        Zein Trabelsi added a comment - before lunch the cancel process the app retrieve the process name + usage type + order type from flowable database (same logic in both platform) . the reason the performance is better in old is that we made flowable database cleanup in staging and we didnt make it in 84 flowable database . 3 queries in flowable database in 84 took > 8s .
        Hide
        Zein Trabelsi added a comment -

        for the senario that return error : its an issue in the process ful-o2p-pstn-002-cancel (uses an unknown variable) , and its fixed and deployed on 84

        Show
        Zein Trabelsi added a comment - for the senario that return error : its an issue in the process ful-o2p-pstn-002-cancel (uses an unknown variable) , and its fixed and deployed on 84

          People

          • Assignee:
            Mbaye Lo
            Reporter:
            Mbaye Lo
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours
              2h

                Drag and Drop