조직 선택
Grades on the Service Appointment (SA) slots have difference between Dispatcher Console Gantt and Service Appointment chatter page
게시 일자: Jan 2, 2024
상세 설명
In problematic org when we compared the responses (browser inspect page) between the 'Dispatcher Console' and the 'Service Appointment Page', we can see that the grades are the same, but on the UI, they appear different.
솔루션
1)
This issue happens because the Service Appointment (SA) is not geocoded, and the lat/long are missing (a valid address could be there). So the grade for the 'Minimize travel' objective in the Gantt action is always 0.
However, in the chatter action (action on the Service Appointment page) we geocode the address using a Google API so we get 100 for the 'minimize travel' objective.
2)
In the HAR logs the action from the SA page has two remote calls - the first one is "CreateOrUpdateService" where we updated the Latitude and Longitude, and the second one is "DoFirstStage" where we calculated the slots and also revert the changes we made in "CreateOrUpdateService".
3)
This is the designed behavior of the product, which allows us to calculate slots without the need to wait for the data.com update (since we have the option to create a service and get candidates for it in the same chatter action or Service appointment page).
In the Gantt, we don't do it because you can't create a SA from there, you can only get candidates for SAs that are on the Service List.
Solution:
There’s no issue with the slot grade and this is working as expected. To get the same grades for slots on Gantt and on the Chatter action (SA from the page) the service appointment should be geocoded.
Note:
To track why the service appointment wasn’t geocoded you can maybe enable history tracking for the Address field to be able to follow the geocode updates.
Knowledge 기사 번호
000694750
이 기사를 통해 문제를 해결했습니까?
개선을 위한 의견을 보내주세요.
