http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-40 L3 Support <p>Kindly can you assist in the SRd reporting as I need the below information:-<br/> 1. SRD’s requests/Completed based on yearly/Staff ID/ Type of service.<br/> As we are reporting below OKR’s we need to map it accordingly, from when the SRD requests come to TAS until all solution is gathered and closed.</p> <p>Design/Optimize economically cost effective, innovative WAN connectivity ( Fixed, FBB, ILL, DIA, MPLS, MPLS GOLD, P2P, VSAT, WFBB, SIP, WIFI, SDWAN, Ethernet P2P) solutions customized for Enterprise Business corporate clients. Ensuring complete end to end design For<br/> • Network Available within 2 working days, <br/> • partial network Available within 6 working days,<br/> • Green field within 14 working days.</p> <p>Design/Optimize economically cost effective, innovative Mobile solutions ( RAN/IBS) customized for Enterprise Business corporate clients. Ensuring complete end to end design For:<br/> • Network Available within 2 working days, <br/> • partial network Available within 6 working days,<br/> • Green field within 14 working days</p> <p>Request raised in GTM</p> LS-40

SLA'S REPORT - GTM 1081

CR Closed Fixed Salem Dannawi Salem Dannawi MS_OT SRD Fri, 18 Oct 2024 10:56:37 +0300 Fri, 23 May 2025 14:22:47 +0300 Fri, 23 May 2025 14:22:09 +0300 Tue, 22 Oct 2024 00:00:00 +0300 0 6 0 minutes 2 weeks, 1 day, 3 hours <p>We will add a new report under the SLA tab called TAS SLA report, which will include the following columns:</p> <ul class="alternate" type="square"> <li>Request ID</li> <li>Assignee(s) of the CONFIRM_SOLUTION task (multiple if applicable)</li> <li>Service type (e.g., MPLS, FBB, SIP etc…)</li> <li>Global SLA (in days)</li> <li>Total SLA (in days)</li> <li>Task Name</li> </ul> <p>Each record will show the duration from the activation date of the CONFIRM_SOLUTION task to the completion of the SOLUTION_ACCEPTANCE task. <br/> The time between these tasks represents the total SLA for TAS, displayed in days (e.g., 2.4 days).<br/> For sure the Total SLA will take into consideration the working hours and weekend / Holidays as configured in SRD. </p> <p>Note: We will modify the current workflow for fixed services to make CONFIRM_SOLUTION the default task after SELECT_SOLUTION. If SSE wishes to bypass this task, they can select the ‘Skip TAS Confirmation’ option in the Service Resource panel.</p> <p>WL : 5 mday</p> <p>starting date: 16-12-2024<br/> actual WL: 6.5 days. </p> <p>Dears,</p> <p>This CR is implemented.<br/> Patch required (3.7.0.1238).</p> <p>Kindly find the attached process to be uploaded.</p> <p>Dear @integration,</p> <p>Kindly apply the following scripts on staging schema. Note that they also exist in patch 3.7.0.1238.</p> <p>Ensure to restart SRD only after applying the queries.</p> <p>Query 1:</p> <p>CREATE TABLE SRD_CUSTOM_SLA (<br/> ID NUMBER(19) NOT NULL,<br/> REQUEST_ID VARCHAR2(100),<br/> TASK_NAME VARCHAR2(200),<br/> TEAM VARCHAR2(100),<br/> ASSIGNEE VARCHAR2(100),<br/> SLA_DAY NUMBER(10),<br/> DURATION_DAY FLOAT(126),<br/> INSERTDATE DATE,<br/> CONSTRAINT PK_New_Table_Name PRIMARY KEY (ID)<br/> );</p> <p>Query 2:</p> <p>alter table srd_task add ASSIGNEE_HISTORY VARCHAR2(255);</p> <p>Query 3:</p> <p>alter table srd_task add VISIBLE NUMBER DEFAULT 1;</p> <p>Regards,<br/> Sara </p> <p>SLA Tasks Report is the new SLA report.</p> <p>The customer is requesting to add the below 2 columns to the new SLA Task Report:</p> <p>the start date when we received this request and end date when we submitted the final solution after going through the workflows.</p> <p>Dears,</p> <p>The requested is implemented.<br/> “Request Type”, “Start Task Time”, “End Task Time” are added as shown below.</p> <p>Patch Required (3.7.0.1244).</p> <p>Dear @integration,</p> <p>Kindly apply the following script on staging schema after applying the patch. Note that it also exists in patch 3.7.0.1244.</p> <p>Query:</p> <p>ALTER TABLE SRD_CUSTOM_SLA<br/> ADD ("START_TASK_TIME" DATE,<br/> "END_TASK_TIME" VARCHAR2(200 BYTE),<br/> "REQUEST_TYPE" VARCHAR2(100 BYTE));</p> <p>Note: In the new columns of time (Start/End Task Time), T: Is A literal character that separates the date (2024-12-12) from the time (12:54:24). It simply indicates that the part after T is the time.</p> <p>we have 2 new bugs here:</p> <p>• Task SLA report should cover open and closed requests<br/> • Task SLA report custom task should reflect the users who participated in the request from TAS team</p> <p>+ check the calculation of the total duration after configuring both working days and hours </p> <p>L3 WL : 4 md</p> <p>Dear @Salem Dannawi<br/> Please make sure that the attached processes are uploaded on staging and prod (SRD). </p> <p>Dear @integration,</p> <p>Kindly find below the queries to be applied by order on the two schemas (staging - prod):</p> <p>Query 1:</p> <p>CREATE SEQUENCE SEQ_SRD_TASK<br/> START WITH -1<br/> INCREMENT BY -1<br/> NOMAXVALUE CACHE 100 ORDER;</p> <p>Query 2: </p> <p>CREATE SEQUENCE SEQ_SRD_REQUEST_EVENT<br/> START WITH -1<br/> INCREMENT BY -1<br/> NOMAXVALUE CACHE 100 ORDER;</p> <p>Query 3:</p> <p>INSERT INTO SRD_TASK (ID, REQUEST_ID, TASK_NAME, TASK_STATUS, TEAM, VISIBLE, INSERTDATE, CHANGEDATE, COMPLETION_DATE)<br/> SELECT<br/> SEQ_SRD_TASK.NEXTVAL, <br/> req.request_id, <br/> 'CUSTOM_TAS', <br/> 'ACTIVE', <br/> 'TAS', <br/> 0, <br/> tas_confirm.completion_date, <br/> tas_solution.completion_date, <br/> tas_solution.completion_date <br/> FROM SRD_SERVICE_REQUEST req<br/> JOIN SRD_TASK tas_confirm <br/> ON req.request_id = tas_confirm.request_id <br/> AND tas_confirm.TASK_NAME = 'CONFIRM_SOLUTION' <br/> AND tas_confirm.TASK_STATUS = 'COMPLETED'<br/> JOIN SRD_TASK tas_solution <br/> ON req.request_id = tas_solution.request_id <br/> AND tas_solution.TASK_NAME = 'SOLUTION_ACCEPTANCE' <br/> AND tas_solution.TASK_STATUS = 'COMPLETED'</p> <p>WHERE tas_confirm.ID IS NOT NULL<br/> AND tas_solution.ID IS NOT NULL<br/> and NOT EXISTS (<br/> SELECT * <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id and tas.TASK_NAME = 'CUSTOM_TAS'<br/> );</p> <p>Query 4: </p> <p>INSERT INTO SRD_TASK (ID, REQUEST_ID, TASK_NAME, TASK_STATUS, TEAM, VISIBLE, INSERTDATE, CHANGEDATE, COMPLETION_DATE)<br/> SELECT<br/> SEQ_SRD_TASK.NEXTVAL, <br/> req.request_id, <br/> 'CUSTOM_TAS', <br/> 'ACTIVE', <br/> 'TAS', <br/> 0, <br/> tas_confirm.completion_date, <br/> tas_solution.completion_date, <br/> tas_solution.completion_date <br/> FROM SRD_SERVICE_REQUEST req<br/> JOIN SRD_TASK tas_confirm <br/> ON req.request_id = tas_confirm.request_id <br/> AND tas_confirm.TASK_NAME = 'CONFIRM_SOLUTION' <br/> AND tas_confirm.TASK_STATUS = 'COMPLETED'<br/> JOIN SRD_TASK tas_solution <br/> ON req.request_id = tas_solution.request_id <br/> AND tas_solution.TASK_NAME = 'SOLUTION_ACCEPTANCE' <br/> AND tas_solution.TASK_STATUS &lt;&gt; 'COMPLETED' <br/> WHERE <br/> tas_confirm.ID IS NOT NULL<br/> AND <br/> tas_solution.ID IS NOT NULL<br/> and NOT EXISTS (<br/> SELECT * <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id and tas.TASK_NAME = 'CUSTOM_TAS'<br/> );</p> <p>Query 5:</p> <p>INSERT INTO SRD_TASK (ID, REQUEST_ID, TASK_NAME, TASK_STATUS, TEAM, VISIBLE, INSERTDATE, CHANGEDATE, COMPLETION_DATE)<br/> SELECT<br/> SEQ_SRD_TASK.NEXTVAL, <br/> req.request_id, <br/> 'CUSTOM_TAS', <br/> 'ACTIVE', <br/> 'TAS', <br/> 0, <br/> tas_confirm.completion_date, <br/> tas_confirm.completion_date, <br/> tas_confirm.completion_date <br/> FROM SRD_SERVICE_REQUEST req<br/> JOIN SRD_TASK tas_confirm <br/> ON req.request_id = tas_confirm.request_id <br/> AND tas_confirm.TASK_NAME = 'CONFIRM_SOLUTION' <br/> AND tas_confirm.TASK_STATUS = 'COMPLETED'<br/> WHERE <br/> tas_confirm.ID IS NOT NULL<br/> AND NOT EXISTS (<br/> SELECT 1 <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id <br/> AND tas.TASK_NAME = 'SOLUTION_ACCEPTANCE' <br/> )<br/> and NOT EXISTS (<br/> SELECT * <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id and tas.TASK_NAME = 'CUSTOM_TAS'<br/> );</p> <p>Query 6: </p> <p>INSERT INTO SRD_TASK (ID, REQUEST_ID, TASK_NAME, TASK_STATUS, TEAM, VISIBLE, INSERTDATE, CHANGEDATE, COMPLETION_DATE)<br/> SELECT<br/> SEQ_SRD_TASK.NEXTVAL, <br/> req.request_id, <br/> 'CUSTOM_TAS', <br/> 'ACTIVE', <br/> 'TAS', <br/> 0, <br/> tas_confirm.completion_date, <br/> tas_confirm.completion_date, <br/> tas_confirm.completion_date <br/> FROM SRD_SERVICE_REQUEST req<br/> JOIN SRD_TASK tas_confirm <br/> ON req.request_id = tas_confirm.request_id <br/> AND tas_confirm.TASK_NAME = 'CONFIRM_SOLUTION' <br/> AND tas_confirm.TASK_STATUS &lt;&gt; 'COMPLETED'<br/> WHERE <br/> tas_confirm.ID IS NOT NULL<br/> AND NOT EXISTS (<br/> SELECT 1 <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id <br/> AND tas.TASK_NAME = 'SOLUTION_ACCEPTANCE' <br/> )<br/> and NOT EXISTS (<br/> SELECT * <br/> FROM SRD_TASK tas<br/> WHERE req.request_id = tas.request_id and tas.TASK_NAME = 'CUSTOM_TAS'<br/> );</p> <p>Query 7:</p> <p>INSERT INTO SRD_REQUEST_EVENT (<br/> ID, RECORD_TYPE, REQUEST_ID, REQUEST_TYPE, TASK_NAME, TEAM, <br/> START_TIME, END_TIME, START_EVENT, END_EVENT, PROCESS_ID, ACTIVE<br/> )<br/> SELECT <br/> SEQ_SRD_REQUEST_EVENT.NEXTVAL, <br/> 'TASK' AS RECORD_TYPE, <br/> tas.REQUEST_ID, <br/> evt.REQUEST_TYPE, <br/> tas.TASK_NAME, <br/> tas.TEAM, <br/> tas.INSERTDATE, <br/> tas.COMPLETION_DATE, <br/> 'TASK_CREATED' AS START_EVENT, <br/> 'TASK_COMPLETED' AS END_EVENT, <br/> evt.PROCESS_ID, <br/> 1 AS ACTIVE <br/> FROM SRD_TASK tas<br/> LEFT JOIN (<br/> SELECT *<br/> FROM SRD_REQUEST_EVENT<br/> WHERE RECORD_TYPE = 'REQUEST'<br/> ) evt <br/> ON tas.REQUEST_ID = evt.REQUEST_ID<br/> WHERE tas.TASK_NAME = 'CUSTOM_TAS'<br/> and not exists (<br/> SELECT * <br/> FROM SRD_TASK tas<br/> WHERE evt.request_id = tas.request_id and evt.TASK_NAME = tas.TASK_NAME)<br/> ;<br/> Commit;</p> <p>1.5 wd</p> <p>After the deployment of patch 3.7.0.1268, the assignee column of the CUSTOM_TASK_FIXED tasks will be filled.</p> <p>Kindly note that the old data will not change. This feature will apply only to new data.</p> <p>@salem , plz validate /confirm below 2 bugs are solved and update the ticket status accordingly</p> <p>• Task SLA report should cover open and closed requests<br/> • Task SLA report custom task should reflect the users who participated in the request from TAS team</p> <p>we will need to update the old data as well with new custom_task_fixed name via script</p> <p>fixed as per internal testing , awaiting customer final feedback , to be followed by with other SLA ticket</p> Actual Start Mon, 16 Dec 2024 04:44:00 +0200 Baseline End Tue, 22 Oct 2024 00:00:00 +0300 Baseline Start Tue, 22 Oct 2024 00:00:00 +0300 Classification Customer Date of Baselining Thu, 19 Dec 2024 04:54:32 +0200 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Tue, 22 Oct 2024 00:00:00 +0300 Planned Start Tue, 22 Oct 2024 00:00:00 +0300 Rank 0|xtig9l: Rank (Obsolete) 9223372036854775807 Severity Support Priority VTDirections