L3 WL : 4 md

ticket partition into 2 parts:
1. FIXED with decimal pint and the exceeded column : 1.5WD
2. MOBILE: 3 WD

Below Points are implemented. Patch Required (3.7.0.1266)

• SLA Duration to be upto only one decimal point.
• ADD a column for the same report to show SLA exceeded flag (True / False)

@integration,

kindly apply the below script on schema:
ALTER TABLE SRD_CUSTOM_SLA ADD EXCEEDED_SLA NUMBER(1);
commit;

The mobile part of the ticket is implemented.

Patch required (3.7.0.1287).

Kindly find attached the modified processes.

Workload: 1.5 days

From: Salem Dannawi <Salem.Dannawi@mobinets.com>
Sent: Tuesday, April 22, 2025 4:41 PM
To: Aya Said <Aya.Said@nuiva.com>; Sara Saddik <Sara.Saddik@nuiva.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Nour Ayoubi <Nour.Ayoubi@nuiva.com>
Cc: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Dawlat Matar <Dawlat.Matar@nuiva.com>
Subject: RE: LS-165_New requirements for SLA Tasks Report

Dear @Sara Saddik,

After checking again, the below request

The Total duration should be 4 days, right? Or how you are calculating the total duration?
And the assignee column still blank for custom_tas as shown

And the assignee column still blank for custom_tas as shown - request ID reference 540

I agree with you on this point, but the customer is requesting to see the assignee name that has completed the CUSTOM_TAS task for example, it’s Marwa for below request, and to calculate the SLA duration for this task from CONFIRM_SOLUTION to SOLUTION_ACCEPTANCE task.

Issue of assignee is fixed.

Patch required (3.7.0.1289)

Email's attached.

Dear Salem,

Kindly find attached the updated process to be uploaded.

@Natnael Asfaw
Kindly to apply the below scripts in order to fix the old data.

Script 1:

UPDATE SRD_TASK task
SET task.insertdate = (
SELECT cs.insertdate
FROM SRD_TASK cs
WHERE cs.REQUEST_ID = task.REQUEST_ID
AND cs.TASK_NAME = 'CONFIRM_SOLUTION'
)
WHERE task.TASK_NAME = 'CUSTOM_TAS_FIXED'
AND EXISTS (
SELECT 1
FROM SRD_TASK cs
WHERE cs.REQUEST_ID = task.REQUEST_ID
AND cs.TASK_NAME = 'CONFIRM_SOLUTION'
);

Script 2:

UPDATE SRD_REQUEST_EVENT e
SET e.start_time = (
SELECT inner_cs.start_time
FROM (
SELECT cs.start_time
FROM SRD_REQUEST_EVENT cs
WHERE cs.request_id = e.request_id
AND cs.task_name = 'CONFIRM_SOLUTION'
AND cs.start_time IS NOT NULL
) inner_cs
WHERE ROWNUM = 1
)
WHERE e.task_name = 'CUSTOM_TAS_FIXED'
AND EXISTS (
SELECT 1
FROM SRD_REQUEST_EVENT cs
WHERE cs.request_id = e.request_id
AND cs.task_name = 'CONFIRM_SOLUTION'
AND cs.start_time IS NOT NULL
);

Script 3:

UPDATE SRD_REQUEST_EVENT e
SET e.insertdate = (
SELECT inner_cs.insertdate
FROM (
SELECT cs.insertdate
FROM SRD_REQUEST_EVENT cs
WHERE cs.request_id = e.request_id
AND cs.task_name = 'CONFIRM_SOLUTION'
AND cs.insertdate IS NOT NULL
) inner_cs
WHERE ROWNUM = 1
)
WHERE e.task_name = 'CUSTOM_TAS_FIXED'
AND EXISTS (
SELECT 1
FROM SRD_REQUEST_EVENT cs
WHERE cs.request_id = e.request_id
AND cs.task_name = 'CONFIRM_SOLUTION'
AND cs.insertdate IS NOT NULL
);

Commit;

The issue is resolved now as customer has requested.

the duration of custom_tas is now fixed as requested by customer:
start custom_tas task from the creation date of confirm_solution till completion date of solution acceptance,