[LS-58] Omantel New Parameter Addition to API for MDU Status- GTM # 1146 Created: 22/Oct/24  Updated: 05/May/25  Due: 31/Oct/24  Resolved: 05/May/25

Status: Closed
Project: L3 Support
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: CR Priority: Deferred
Reporter: Salem Dannawi Assignee: Abir Messaikeh
Resolution: Fixed Votes: 0
Labels: MS_OT
Σ Remaining Estimate: 0 minutes Remaining Estimate: 0 minutes
Σ Time Spent: 2 days Time Spent: 2 days
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: XML File OT MDU.xml    
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
LS-280 Omantel New Parameter Addition to API... Technical task Cancelled Khaled Khalil  
Customer:
OMAN-Tel
Planned Start:
Planned End:
Severity: Minor
Actual Start:
Date of Baselining:

 Description   

To capture the new field we will need ESB and NEP changes to be implemented

@OBC Switching Support , please raise GTM to accommodate this request.

Regards,
Yasssin

Omantel - Concealed
________________________________________
From: Ahmed Al Battashi <Ahmed.Battashi@withaq.om>
Sent: Monday, August 12, 2024 10:38 AM
To: Yasssin Geehad <Yasssin.Geehad@omantel.om>; Ahmed Abdullah Hamood Al Harthi <ahmed.harthi3@omantel.om>; Ahmed Salim Mohammed Al Abri <ahmed.abri1@omantel.om>
Cc: Waleed Al Abri <waleed.abri@omanbroadband.om>; Ahmed Al Hasani <ahmed.hasani@withaq.om>; Arwa Al Jabri <arwa.jabri@omanbroadband.om>
Subject: Omantel New Parameter Addition to API for MDU Status

[EXTERNAL] - This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dear @Yasssin Geehad & @Ahmed Abdullah Hamood Al Harthi
I hope this message finds you well.
I am writing to inform you that we will be adding a new parameter to our API to enable the sharing of MDU (Multi-Dwelling Unit) status. The parameter name is "mdu_status". Sample is attached.
This addition is intended to enhance our data sharing capabilities and provide more detailed information through the API.
Please let us know if you require any further details or have any questions regarding this update. Development will completed and will start UAT on 26 August.
Thank you for your cooperation.
Best regards,

 Comments   
Comment by Dawlat Matar [ 29/Oct/24 ]

as i understood, we should add a new parameter (mdu_status) to the API updateOBCTaskStatus, but its functionality is not mentioned. so kindly mention what shall we do with this parameter ?

Comment by Abir Messaikeh [ 04/Nov/24 ]

Please note the below changes required.

• Add additional field under the OBB remarks section and also the last update in OBC report to display the update in MDU_Status parameter.

Additionally for the same API we need to capture the attachments passed by OBB which is currently being passed but not stored in FN.

Dear @Amir Mohammad Ali Talebi ,
As discussed , Kindly raise separate GTM for this requirement.

Below is example payload from OBB , the attachment file content (base64) format and file name are highlighted in below params.

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:obc=http://omantel/services/obcservice> <soapenv:Header /> <soapenv:Body> <obc:updateOBCTaskStatusRequest> <OT_EAI_HEADER> <MsgFormat>OBC</MsgFormat> <MsgVersion>1</MsgVersion> <RequestorId>ITSOBC</RequestorId> <RequestorChannelId>W</RequestorChannelId> <RequestorUserId>ITSOBC</RequestorUserId> <RequestorLanguage>E</RequestorLanguage> <RequestorSecurityInfo></RequestorSecurityInfo> <EaiReference>0</EaiReference> <ReturnCode>0000</ReturnCode> </OT_EAI_HEADER> <Request> <ReferenceNo>OT-BEUC-R-ConnONT-01680269</ReferenceNo> <Unable to render embedded object: File (--> <ErrorCode></ErrorCode> <) not found.-Optional:> <EstimatedCompleteDate>2024-04-22T10:56:21</EstimatedCompleteDate> <Unable to render embedded object: File (--> <InstalledPlanDate>2024-04-22T10:56:21</InstalledPlanDate> <) not found.Optional:> <OBCTag>40RDN5061825331//OT534653</OBCTag> <Unable to render embedded object: File (--> <Remarks></Remarks> <FINSOrderNo>182971406</FINSOrderNo> <UpdatedBy>BSS OBC UpdateStatus</UpdatedBy> <) not found.Optional:> <SurveyAppointmentDate>2024-04-22T10:56:21</SurveyAppointmentDate> <Unable to render embedded object: File (--> <SurveyCompletionDate>2024-04-22T10:56:21</SurveyCompletionDate> <TaskStatus>Installation Tested and Complete</TaskStatus> <) not found.Optional:> <ONTSerialNo>485754439910D4AD</ONTSerialNo> <Unable to render embedded object: File (--> <ONTMake>OBC</ONTMake> <) not found.Optional:> <handsetSerialNo>NOT APPLICABLE</handsetSerialNo> <Unable to render embedded object: File (--> <handsetMake>NOT APPLICABLE</handsetMake> <) not found.Optional:> <fileContent></fileContent> <!Optional:-> <fileName>installation_evidence_20240409055905479.pdf</fileName> </Request> </obc:updateOBCTaskStatusRequest> </soapenv:Body> </soapenv:Envelope>

Comment by Sara Saddik [ 17/Mar/25 ]

Subject: LS-58 : Omantel New Parameter Addition to API for MDU Status- GTM # 1146 // LS-169: GTM# 1146(Request to Save Attachments from updateOBCTaskStatus in NEP)

Dears,

These two tickets are implemented.
Patch Required (3.7.0.1273)

@integration,
Kindly to apply the below two scripts on schema
First Script:
alter table FN_OT_OBC_TASK add MDU_STATUS VARCHAR2(255);
Second Script:
ALTER TABLE FN_OT_OBC_TASK
ADD (FILE_CONTENT BLOB,
FILE_NAME VARCHAR2(255));

Regards,
Sara

Comment by Sara Saddik [ 17/Mar/25 ]

One remark from sara , MDU status was added only on obc task report for now , not obc report , this can be completed on Monday

Comment by Abir Messaikeh [ 18/Mar/25 ]

start dev = 3 Mar
End dev = 13 Mar

Comment by Abir Messaikeh [ 26/Mar/25 ]

real WL = 2md

Comment by Abir Messaikeh [ 05/May/25 ]

Applied on PROD

Generated at Wed Apr 15 14:22:43 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.