-
Enhance Email Functionality in Work Orders for Field Service
Suggested by Bérangère DUVAL – New – 0 Comments
We have identified a significant gap in the functionality of Microsoft Field Service that we believe, if addressed, would greatly enhance user experience and efficiency. Currently, when creating an email from a work order, the system does not automatically populate the "To' field.
This feature is available in other tables such as incidents and opportunities, but not in work orders.
Upon contacting Microsoft Support, we were provided with a script to manually add to our forms, as this functionality is not available out-of-the-box. While this workaround is appreciated, it is not an ideal solution for all users.
It would be appreciate to have a standard feature that automatically populates the email recipient field with the contact specified in the "Reported By" field, or with the service account if the contact is empty. This enhancement would streamline the process, reduce manual entry errors, and save valuable time for Field Service users.
-
Time input to be related to Resource Requirement's Time Zone
Suggested by David Shaw – New – 0 Comments
Hi all,
Regarding URS, it seems the Time From Promised and Time To Promised fields don't respect the Time Zone on the Calendar/ Work Hour Calendar of the Resource Requirement but rather the time zone of the User and/or device inserting the value. This is does not seem to be consistent nor intuitive when explicitly selecting the time zone of the resource requirement and then having to calculate the time difference of you (the user) and the RR's time zone when inserting the start time. Surely a better design would be to treat the Time To/From Promised as RR Time Zone related and not inserting user related as it makes it very difficult for central planners operating across many time zones requiring them to always calculate time differences or to keep switching their personal time zone to match the RR time zones they are booking.
Furthermore I have noticed that when inserting a value a Time Window Start and saving, the Time Zone value of the inserting user is automatically populated in the Time one for time window field rather than the Resource Requirement's calendar time zone, adjusting this has no effect, just adding more confusion to the design.