Reachable in menu via Settings=> Business Management.
If you’re opening the form from Unified Interface you’ll see the lookup field Organizational Unit on the form.
But if you’re opening it from the former UI you’ll get another lookup field Site instead:
So is Organizational Unit the “newer” replacement for Site (at least when it comes to Field Service?
If you are creating a Bookable Resource with Resource Type Equipment than the Organizational Unit gets automatically populated from Facility/Equipment.’Organizational Unit’ into ‘Bookable Resource’.’Organizational Unit’.
There is a Work Hours ribbon button in Unified Interface:
If you’re going to enable another (custom or OOB) entity for scheduling there is a great blog series from Sara Lagerquist (see links below) which has some good tips. Based on these tips I’m listing up some of the most valuable insights when it comes to extend URS functionality when you Enable Resource Scheduling for Entities.
don’t create new relationships from within the “Enable Scheduling” setup wizard as they won’t contain your custom prefix in their technical relationship names
think about doing a more sophisticated field mapping by Workflow instead of only using the static field mapping from the wizard
also take into account to leverage the standard field mappings for the newly created relationships to pass on additional parameters which are not exposed as fields in the wizard
don’t forget to maybe auto create Resource Requirements by another Workflow
also you maybe want to auto-populate Resource Requirement Skills / Characteristics for your new Resource Requirements
for only a limited number of Characteristics you might want to create several new Lookup fields on your newly schedulable entity to the Characteristic entity
for a larger number of Characteristics you could use Microsoft Flow to populate them into your Requirement Characteristic entity. Source for this Characteristics list to be picked up by Flow could be a new sub-entity from your newly schedulable entity (NewSchedulableEntity 1:n NewSchedulableEntity.Characteristics). If you want to make Service Tasks schedulable you could alternatively use the Service Task Type and place a new Subgrid “Service Task Type Caracteristics” there.
Say you add the Contact subgrid into your Account form on Field Service Mobile because you’re expecting your Field Agents to also capture new Contacts and they are first searching for the Account first instead of adding the Contacts directly from Home=>Contacts.
Now if you tab on “+” at the top of the Contacts subgrid on the Account form the “New” form for Contacts opens.
And now the difference here is: if you leave the setting from below in its standard configuration as it comes out of the box, your address fields will stay empty so that for the new Contact you have to fill everything in manually.
But if you change the setting “Use Entity & Attribute Map” to “true”, the address fields on a new Contact form are automatically populated from the same fields on the Account form were you had started your journey.
Here is a nice article by Thomas Dayman that gives a short overview of how to embed a Survey Questionnaire created with the new Microsoft Forms Pro into the Field Service Mobile app. The approach is to create an Offline HTML file where Thomas provides a sample code snippet for, and embed that via iFrame into a Form in Woodford.
Compared to Resco’s new Inspections the Forms Pro integration doesn’t support offline scenarios. Resco Inspections comes with additional licence cost whereas for Forms Pro it is still not clear how the licencing will look like.