#FSLOfficeHours When using Polygons, the SA gets its Service Territory via the polygonUtils call when the SA is geo-coded. This does NOT result in the (parent record) WO also getting Service Territory.
Are there disadvantages of us leaving Work Orders (or WOLIs) with Service Territory Blank? (Sharing, etc)?
What is the recommended way of setting the WO ST to match the SA? Simply Process Builder on SA after the ST may be set?
Hey @Bruce Stewart per our conversation on Office Hours today. Outside of potential reporting there really isn't any downside to the Service Territory only being on the SA, as it would be set by Polygons upon creation.
Only caveat would be how you are sharing the records to the various users. If you are using User Territory Based sharing, there shouldn't be any issue as access to the Resources, Appointments, Work Orders are based on the membership in the appropriate public group and would be looking at the ST on the Service Appointment, then the Parent Work Order would get shared based on the FSL Settings to share Parent Work Orders as well.
If there is some type of Custom Sharing Model in place, that specifically is based on the ST Field on the Work Order, then you'd probably just want some automation, as you have outlined, to go and set that ST value after it is set on the SA.
