FSM Configuration Settings (Admin)

Mobileforce Field Service Management (FSM) can be configured with the following settings which govern the behavior of the Schedule and Dispatch screen.

Please note: The settings described herein can only be set and modified by Mobileforce FSM Administrators. For help with these settings, please contact your Mobileforce FSM Administrator.

This screen allows a dispatcher to schedule service tasks within an office. A user-friendly
UI displays these scheduled task in a calendar. Also, the locations of tasks and
technicians are displayed within a google street map.

The key objects used by the Schedule & Dispatch object
are as follows:

UI

There is no top-level screen type because Schedule and Dispatch is designed to be an inner screen that is invoked after selecting an office.

The URL for the dispatch and schedule screen is

scheduledispatch.php?path=...&s=...&officeId=...

It requires three parameters, path, s, and officeId. path and s are the standard
adlwebui parameters. officeId is the ID of the office EasyCLM object to schedule for.

There are two ways one can configurer the schedule & dispatch screen, depending
on whether the application has one office or multiple offices

Configuration for a single office scheduling

For single-office scheduling, the office ID is hard-wired into the URL. The adlwebui-extension
property causes the web screen to go directly to the given URL instead of using an iframe.
Also, it will automatically append the path and s parameters.

<screen type="web" name="Schedule &amp; Dispatch"
        iconportrait="..." iconlandscape="..." acl=""
        url="https://apps.mobileforcesoftware.com/adlwebui/scheduledispatch.php?officeId=1" >
  <data>
    <prop key="screenid">scheddisp</prop>
    <prop key="param-prefix">easyclm-</prop>
    <prop key="adlwebui-extension">1</prop>
    (other props)
  </data>
</screen>

Configuration for multiple office scheduling

For multiple-office scheduling, the top-level Schedule & Dispatch screen is a datatable screen that
displays all offices. It is configured such that clicking on a office will open
the schedule & dispatch screen. Also, updates are disabled for this screen.

<screen type="datatable" name="Schedule &amp; Dispatch"
        iconportrait="..." iconlandscape="..." acl=""
        url="https://apps.mobileforcesoftware.com/adapters/easyclm/schema.php#Office" >
  <data>
    <prop key="screenid">scheddisp</prop>
    <prop key="param-prefix">easyclm-</prop>
    <prop key="listitem-link-template-Office">scheduledispatchscreen.php?[[]]&amp;officeId=[id]</prop>
    <prop key="table-actions-Office">list</prop>
    <prop key="content-body-header">Please select an office.</prop>
    (other props)
  </data>
</screen>

Customizing displayed fields

The Schedule & Dispatch screen displays detailed data from tasks, technicians, and appointments.
Customers may need to change what info is displayed by default, perhaps showing custom fields.
To support this, the Schedule & Dispatch screen uses datatable layouts to allow customization
of list data, popups, and detailed info.

To customize a particular list, popup or object details, create a layout with the layout type set
to 'scheduler'. (This layout type can be changed via the configuration property 'layouttype'). The table
below shows which UI component map to which layouts

Customizing global action buttons

Scheduling often requires customized actions, such as autoscheduling or custom-built tools
for a customer. To support this, the Schedule & Dispatch screen allows one to add custom
global actions buttons to the top right of the screen. This is done via configuration properties
of the form action-button-{id}, where {id} is an unique identifier for the button.
The value of the button is a tuple of value separated via the pipe ('|') char. The values
of this tuple are as follows:

• Displayed label for the button
• (optional) Target for the button. Can be 'link', 'tab', or 'window'.
  • If 'window', (the default), a new window will be opened to display the target link.
  • If 'tab', the link will open in a new tab
  • If 'link', the link will open in the current page
• (optional) Additional CSS class(es) to add to the button.
• Link to go to when the button is clicked. The path, s, and officeId parameters will be automatically added to this URL.

Some example properties are:

<prop key="scheduler-action-button-plugRoute">Plug Route|https://apps.mobileforcesoftware.com/customers/servicevelocity/servicevelocity/calendar/scheduler/php/plug_route.php</prop>
<prop key="scheduler-action-button-smartRoute">Smart Route|https://apps.mobileforcesoftware.com/customers/servicevelocity/servicevelocity/calendar/scheduler/php/smart_route.php</prop>
<prop key="scheduler-action-button-mapAppointment">Map Appt.|https://apps.mobileforcesoftware.com/customers/servicevelocity/servicevelocity/calendar/scheduler/php/mapAppointment.php</prop>

Configuration properties

The Schedule & Dispatch screen can be customized through several properties that can be either in the screen itself, or in the parent app or applet elements. These properties can also be prefixed either by the screen's parameter-prefix, specified by the param-prefix screen property, or by the global scheduler- parameter-prefix. This parameter prefix is optional when specified within the screen but required in the app or applet elements. For example, the property min-range can be specified as just min-range within the screen element, or as scheduler-min-range or easyclm-min-range when specified within the screen, applet, or app elements. This example assumes that the screen prop param-prefix is set to easyclm-.

The table below lists all supported configuration properties