Details
-
Type:
Bug
-
Status:
Ready for QA
(View Workflow)
-
Priority:
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
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2026-03-03 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2026-03-03 24:00 (milestone: set planned end date to due date) |
| Description |
Cancelling WO with one task “Switching ADSL” is completed is not working. See WO 4444900281
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>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> |
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> |
| Assignee | Hassan Abdine [ habdine ] | Ayed Bada [ abada ] |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Assignee | Ayed Bada [ abada ] | Zein Trabelsi [ ztrabelsi ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Zein Trabelsi [ ztrabelsi ] | Mbaye Lo [ mbayel ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour [ 3600 ] | |
| Worklog Id | 293722 [ 293722 ] |
| Baseline Start | 2026-03-03 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2026-03-03 24:00 (set baseline based of initial work logging) |
| Time Spent | 1 hour [ 3600 ] | 2 hours [ 7200 ] |
| Worklog Id | 293722 [ 293722 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1d 18h 56m | 1 | Ayed Bada | 05/Mar/26 7:01 AM | |||||
|
6s | 1 | Ayed Bada | 05/Mar/26 7:01 AM | |||||
|
4h 55m | 1 | Zein Trabelsi | 05/Mar/26 11:57 AM | |||||
|
21h 49m | 1 | Khaled Khalil | 06/Mar/26 9:47 AM |
|
Links Hierarchy |
Documentation
|
Documentation
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 .