#Multi-day0 discussing

Hi @Steve Hupp /All -

We have use case where 

1.Technicians are travelling by air within USA and working on appointments in other corner from his/her home location(assuming they are secondary resources on multiple territories) and 

2.Additionally - these same technicians can work on local appointments(in Primary territories and can travel by Car) whenever it's needed.

3.Point to mention is - Mostly Appointments are multi-day.

Now -

1. Whenever they are travelling locally - gantt is showing Travel time correctly (Start and End ) - Working as designed.

2.In case Air travel we don't want gantt to show and Scheduler Engine to block resource time - As we know - for air time we cant predict travel details and its not even supported in Product.

e.g. here by using resource address and Appointment address, resource are getting blocked for entire week using default travel calculation and dispatcher /optimization will not able to use that travel time period to book other appointment(except if we forcibly book using drag-drop with rule violation).

3.In reality resources are travelling by air and we are planning to show resources air travel(to and from air travel dates-entire day and  these dates are with SA start and End date- we can easily figure out total duration and travel duration - this is also working good with some customization) on gantt by using Resource Absence with new value in Picklist type - Travel/xyz.

3.In order to Prevent automatic travel calculation - I am thinking to remove address from SA if resource is planning to travel by air.- In this case Scheduling will not calculate to and fro travel time and resource will be available for other Appointments during that period.

Could you please suggest if you any better/alternate solution for this work in order to ignore travel time calculation for long distance/air travel appointments.

CC: @Leigh-Anne Nugent

#SFS #FSLOfficeHours #FSL #Multi-day #AirTravelling #Fsl Scheduling #TravelTime  

Hi All -

We have scenario where -our business team is looking to clone Service Appointment and assign to the same resource of original appointment. Expected to action on dispatch console,

- We have created custom action and from backend we are handling clone and resource assignment.

- This use case is working as expected for non-Multiday appointment (Is Multiday checkbox is unchecked)

- We are getting following error if we try to schedule/assign resource with same action.

1st Issue:

=============

caused by: FSL.Exceptions.GeneralException: Service Appointment 08p010000003I37AAE status is included in pinned statuses, therefore it could not be auto scheduled. Class.FSL.SAWrapperGetSlots.checkIfServiceValid: line 64, column 1 Class.FSL.SAWrapperGetSlots.<init>: line 13, column 1 Class.FSL.MdtSchedulingUtils.getUpdatedMdtServiceLength: line 322, column 1 Class.FSL.MdtSchedulingUtils.getUpdatedMdtServiceLength: line 101, column 1 Class.FSL.MdtSchedulingUtils.updateMdtServiceLength: line 47, column 1 Class.FSL.LogicUtils.updateMdtFinishDate: line 1100, column 1 Class.FSL.TR021_AssignedResourceUtils: line 2500, column 1 Trigger.FSL.TR021_AssignedResource_AfterInsert: line 28, column 1: [] 14:49:19.304 (2304731511)|USER_DEBUG|[56]|DEBUG|Service Appointment Clone exception >> System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, FSL.TR021_AssignedResource_AfterInsert: execution of AfterInsert

for this error- I referred FSL trigger doc- https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_dev_custom_triggers.htm

It has 1 point related to the multiday -(If the created resources’ service is a multi-day service appointment, this trigger checks if it’s necessary to recalculate the service duration. If so, the trigger recalculates the length.) - but did not found anything related to this error/ reason behind this failure

=====================

however Current status(Status name = Initial, Status Category- None)(before Scheduling) in not marked as pinned under Field Service Setting->Scheduling->General Logic ->Select which statuses are considered as pinned, or unmovable, for scheduling.

Also -

2nd issue:

- We are unable to Edit/update these Service appointments if Status is checked/listed/marked under Field Service Setting->Scheduling->General Logic ->Select which statuses are considered as pinned, or unmovable, for scheduling. (This also happening for multiday appointments)

However - based on my understanding allowing Edit/update SA is depending upon FSL__Pinned__c SA field .

and above mentioned configuration says-  Pinned statuses are pinned from the perspective of automated scheduling, not manual Scheduling or manual update.

need help to resolve above details - so that we could unblock our work progress.

@Steve Hupp @Leigh-Anne Nugent @Dustin Breese 

#Multi-day #Multiday #Service Appointments 

Hi All,

Scenario:

For Multi-Day Service Appointment

2 week Appointment- 80 Hrs - Starting from First week's Monday to 2nd Week's Friday

Added Resource availability work rule into Scheduling Policy

Territory Operating hours has - Times slots defined Monday to Friday - 8 hours every day

No Operating hours has been added to the STM

Challenge facing - 

-Candidate feature is not showing any resource

-shows Candidates only if Resource availability work rule removed from Scheduling Policy(which is not desired behavior)

-If We add Saturday and Sunday - 8 hrs then Candidate functionality showing candidates and if wee book for any candidate - appointment is getting booked from first week Monday to 2nd Week Wednesday - which is expected because of 7 day week slot(this is not our business case- we need 5 day week)

Functionality expected:

keeping Times slots only Monday to Friday - 8 hours every day and candidate functionality should show technician availability over the period of 2 weeks

are we missing something  or this is limitation for multi-day appointments ?

how we can achieve this functionality/functionality should show technician availability for multi-week appointments(with 5 day working week)

Let me know if you have questions.

Thanks,

Satish

CC: @Steve Hupp @Dustin Breese 

#FSL #FSLOfficeHours #SFS #Multi-day