Wednesday, September 18, 2019

Work Rule of Record Type: Field Service - Excluded Resources

Sometime Customer does not want to work with some selected Service Resource(s) due to bad feedback or bad experience. So, here we can use this “Excluded Resources” work rule to meet the requirement.

How to crate:

Go to Work Rule tab and click "New" button to create a new Work Rule. Then select record type as “Field Service - Excluded Resources” and then click “Next”. Then give the Work Rule Name and its Description.





Note: While installing FSL packaged, system will automatically provide a Work Rule record name as “Excluded Resources”. So, we can use this as well.



Note: For this example, I will work on existing record to make this discussion to the point. Because here our aim is to check, exclude work rule behaviour, but not to create a Work Order or Service Appointment or Scheduling Service Resource etc.


Now from “App Launcher“ select “Field Service” app. Now for my case I am opening Work Order (00000017). For this work order (00000017) we have already a Service Appointment (SA-0017).



Then click on “Field Service” tab, then click on “SA-0017”, and finally click on “Candidates” button.



Check there is four Service Resources are available for appointment and they are
  1. Alan Reed, 
  2. Martino Castanon, 
  3. Paul Morrison, 
  4. Ralph Clark.

Now, let say Customer doesn’t want to work with “Alan Reed”.



So, here we can use this exclude work rule to fulfil the scenario.

Go to Related section of Work Order (00000017) and click on “New” button of “Resource Preferences” and then add “Alan Reed” as “Excluded” preference type.





Now the final touch รจ Go to “Field Service Admin” app and click on “Filed Service Settings” > “Go to Guided Setup” > “Scheduling Policies”.

Select your Scheduling Policy and then add work rule “Excluded Resources” from Available Rule to Selected Rule.



So, we have done. It is ready for testing.

Now again click on “Field Service” tab and open dispatch console and check candidates for “SA-0017”.
So, as per expected behaviour excluded resource (Alan Reed) will not be shown in dispatch console.


LWC to LWC Communication using Lightning Messaging Service (Part - 2)

In my previous post ( previous post link ) we have learn how to create a Lightning Messaging Service with 6 steps and today we will use the ...