Enhance the condition of invalid WOT records check [Backport for DEF0546121]DescriptionWhenever a WOT has an invalid state combination, the calendar may go completely blank and not load at all. This primarily happens for tasks that are assigned to techinicians as those are the tasks that are visible on calendar. Whenever dispatcher workspace encounters this task, the way the payload is prepared it contains bad data / bad configuration due to which the calendar encounters a null pointer exception Page refresh may not resolve this issue because the erroneous payload is passed to calendar even after page load. Various situations can cause this issue: Bad data that includes issues like: start of a work order task is before end, Start or end values on a task are missingInvalid state combination that lead to bad data: Task is assigned to technician so state = "Assigned" but substate is "On route" . A technician cannot be assigned a task and be on route at the same time. This causes null data issueSteps to Reproduce 1) Create a WOT and move it to Assigned State.2) Make State=Assigned and SubState=OnRoute (incorrect datasetup some customer instance has this kind of data)3) Observe that DWS keeps on spinning.Expected: Any invalid WOT should get skipped from being displayed on DWS and DWS should load fine.We need to enhance the condition of invalid WOT records check to gracefully handle invalid data set up and prevent DWS spinning issuesWorkaroundThe defect fix is backported up to Xanadu patch and DWS version 26.0.11. Only workaround available is to upgrade to that version of dispatcher workspaceRelated Problem: PRB1795954