@* Salesforce Field Service * Experts,
Can we customize the violation warning message on SA when a SA is scheduled manually, if it doesn't match the required skill?
Thanks in Advance
@ganesh pelluri Rule Violation messages can be customized from Custom Labels. For Match Skills rule, you can add a 'New Local Translations/Overrides' in the RuleViolation_Match_Skills:
I recently created a flow that launches when a Service Appointment (SA) of a certain Work Type is marked complete. It creates a new SA for the same time on the next day. It moves through the statuses from none->scheduled->dispatched. It assigns the resource and shows up on the Gantt as it is supposed to. The problem is I get a rule flag as seen in the screenshot however, this is incorrect as the skill is assigned to the resource. If I drag it to another resource and drag it back it will clear the rule. Any ideas?
#Field Service #FSL Gantt #Service Resources #Rule Violations #Service Appointments #Skills
Yes, I have. I can schedule the same appointment without using the flow and I don't get the flag. I have been using that work type and resource combination frequently in tests.
I saw where I set my scheduled end time with the same variable that set the scheduled start time by mistake. I corrected this to set the end using start time + duration and now the Match Skills violation doesn't occur. I'm not sure what they have to do with one another, but it seems that corrected the issue. Thanks for your inquiry.
Hello experts,
We need to prevent dispatchers from manually dragging a SA from one ServiceTerritory to another different ServiceTerritory, but we found out that Scheduling Policies and Rule Violations are not really avoiding it but only warning, is there any way to prevent the users from doing this?
If this cannot be acomplished, is there any way to colour-code these SA with the Match Territory rule violation in red?
Thank you!
I believe you could accomplish through a Trigger (initiated with a Assigned Resource Record being updated) using prior value on the Service Resource, querying their Service Territory Member record, grab the territory Id, and compare to the same for the new resource.
However, I also believe you could accomplish with a 2 part declarative automation.
First would be a before save flow (again that initiates off an AR Update) that does the same as the trigger above. Grabs the previous value of the Service Resource, Fetches the STM, Grabs the Territory, and compares to the New Resource's Territory.
If Different it checks a custom checkbox field on the AR record (as before save flows can't update other records)
That checkbox being updated then kicks off a second automation(after save flow) to grab the SA off the Assigned Resource, and then update the Gantt Color Field with a specific Hex Value so you can clearly see where those instances have occured.
I tested the first part on my side (before save flow) and it worked (
https://unofficialsf.com/how-to-use-ischanged-and-priorvalue-in-before-save-flows-by-gorav-seth/)
Depending on your data volumes I might recommend the trigger route as that is better for scalability, but if volumes are not a concern I definitely feel like this can be achieved through declarative automation.
There would be some considerations for sure like do you clear out the checkbox on the AR record after the SA update, so that it can be rechecked if it happens again. And there may be a way to initiate it off of the SA update as well, but would need to dig deeper.
Hope that helps!
Hello everyone,
Has anyone had any luck or experience reporting on Work Rule / Policy violations?
Now that we have been using FSL for over a year we are looking to refine our skill assignment as well as do an audit of our Work Rules and Policies to see if it makes sense to revise them. Our schedulers are mostly still relying on tribal knowledge and manual scheduling as opposed to using the Get Candidates feature or moving to automated scheduling. Since we still have several rule violations we would like to do analysis and see the root cause as we'd like to move towards a more automated / guided process.
One of the ways we were thinking about doing this is running a report on all dispatched Service Appointments with Rule Violations. Rule violations don't appear to be stored in a field on the SA nor be an object that I can find reference too. Has anyone been able to create a similar report or is there an alternative method to performing this analysis you might know of?
Dear all,
is there a possibility to generate a report from the rule violations from the Gantt (dispatch console)?
