[ACE-627] Cancelling WO with one task “Switching ADSL” is completed is not working. Created: 03/Mar/26  Updated: 10/Mar/26  Due: 03/Mar/26

Status: Ready for QA
Project: ACE
Component/s: FN
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Mbaye Lo Assignee: Mbaye Lo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 hours
Original Estimate: Not Specified

Customer:
OMAN-Tel
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 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>

 Comments   
Comment by Zein Trabelsi [ 05/Mar/26 ]

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 .

Comment by Zein Trabelsi [ 05/Mar/26 ]

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

Generated at Wed Apr 15 13:11:13 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.