search

meridianww / M4PLBase

0 stars 1 forks source link

Job Gateway Status Displaying Incorrectly #293

Open nmfujimoto opened 4 years ago

nmfujimoto commented 4 years ago

The Job Gateway Status is showing the last record added to the Tracking tab, but should only be showing the last Gateway record.

nmfujimoto commented 4 years ago

image

nmfujimoto commented 4 years ago

Still see this issue in production: image

nmfujimoto commented 4 years ago

@bharathrl The image below is the top 10 most recent Jobs in the Production system and they are still showing XCBL-GPS Coordinate as the Job Gateway Status. The XCBL-GPS Coordinate is an Action not a Gateway, the correct Job Gateway Status for the jobs is In Transit.

image

bharathrl commented 4 years ago

We will check and update this.

CC - @radha4116 @KamalAdhikary

radha4116 commented 4 years ago

Verified this issue and created a one more bug reference is 325 hence closing this issue

nmfujimoto commented 4 years ago

Please run a script to update existing Gateway Status to only be Gateway type records. Once this is performed in Dev we will use the same script to update Production.

nmfujimoto commented 4 years ago

@bharathrl This issue has been open for 25 days now in Production and is becoming unacceptable. I need the team to please explain why this has not been corrected. We need the Job Gateway Status field to display correctly as that field is in the grid for Jobs, Reports, and Dashboards.

nmfujimoto commented 4 years ago

@bharathrl @prashantaggarwal1999 My last comment was a week ago and now the issue has not been resolved in over a month. How are users supposed to trust the Gateway Status when it is incorrect? I have asked repeatedly to have this fixed as it is affecting users in production, but we are not making any progress. Thoroughly frustrated with the progress.

Here are the most recent orders created in production: image

prashantaggarwal1999 commented 4 years ago

@nmfujimoto I think we have identified the issue here, there is one stored procedure with name CopyJobGatewayFromProgramForXcBL which is getting used to update the actions while receiving an xCBL request. When we are receiving an xCBL request then there is no use case where we need to update the Job Gateway Status so ideally Gateway Status update should not be there. Removed the Status updated from the Stored procedure, I hope it will not create the wrong data now, will update the existing data.

prashantaggarwal1999 commented 4 years ago

@nmfujimoto Query which has been used to fix the issue was:

UPDATE JOB SET Job.JObGatewayStatus = Gateway.GwyGatewayCode From JOBDL000Master job INNER JOIN ( SELECT Max(Id) GatewayId,JobId FROM JOBDL020Gateways Where GatewayTypeId = 85 GROUP BY JobId ) GatewayName ON GatewayName.JobId = Job.Id INNER JOIN JOBDL020Gateways Gateway ON Gateway.Id = GatewayName.GatewayId Where Job.JObGatewayStatus <> Gateway.GwyGatewayCode

prashantaggarwal1999 commented 4 years ago

Corrected Data Job List.xlsx

Here is the list of Jobs for Which Data Has Been Corrected.

kirtya commented 4 years ago

Feature has been developed and testing is in progress.