Application-Level Control of Properties

Mobileforce provides CRM-based solutions, which can be customized to suit the needs of every organization. Additionally, Mobileforce provides many application-level features and properties that may not be applicable for every customer or organization.

If you want any of the properties listed below enabled or disabled, please contact Mobileforce support.

Mobileforce Configure, Price, Quote (CPQ) properties

Since Configure, Price, Quote is a well defined application, its components, structures, and their properties are also well documented. The following API specification provides methods for reading and updating various objects that are manipulated by the CPQ Application: such as Products, Quotes, and Pricing.

The APIs documented here provide the most common operations such as Create, Read, Update, Delete, List, Search. Please contact Mobileforce support for help in setting up various properties relating to the CPQ Application

Mobileforce CPQ APIs

Update CRM fields when writing a quote to CRM

Whenever a quote is written back to CRM, you can configure Mobileforce CPQ to specify specific properties (fields) of an object that need to be updated.

When a CRM provides a "deal" (or opportunity") object, then you can specify the property: crm-deal-properties-to-update. For example, for Hubspot, the specific property is hubspot-deal-properties-to-update

Here's how you'd use this property (assuming the deal has two fields: Deal Type and Balance Due.

<prop key="hubspot-deal-properties-to-update">{"Deal Type" : "cpq_dealtype", "Balance Due" : "cpq_balance_due)"}</prop>

Mobileforce Field Service Management (FSM) properties

Since Field Service Management (FSM) is rather expansive and includes many (often disjoint) capabilities, the description of the properties that control the behavior of FSM is also expansive and by no means intended to be a complete specification. Listed here are some of the most commonly used properties of Mobileforce FSM application.

Single Office vs Multiple Office

This property affects the Schedule & Dispatch Screen.

If set to Multiple Office, the Schedule & Dispatch Screen at the very top provides a drop down for the Dispatcher to select a specific office (from amongst the many offices that you may have). Alternatively, The Screen can also be customized so specific dispatchers (depending on their level of Access Control) can only see specific Offices. In addition, the selection of the office also determines (a) which service tasks are shown in the service tasks section (these are the tasks assigned to that specific office) and (b) which technicians are shown in the technician/calendar section (these are the technicians assigned to that specific office). In addition the map view also shows a view port around the specific address of the selected office. All these dependent sections of the Schedule and Dispatch screen change when a different office is selected.

If this property is set to single office, then the Schedule & DIspatch screen only shows that single office, with service tasks for that office, and technicians assigned to that office. Additionally, the map view shows a view port of that specific office, along with the surrounding areas.

Please contact Mobileforce Support to customize this setting for your business' specific needs.

Customizing displayed fields

The Schedule & Dispatch screen displays attributes of tasks, technicians, and appointments.
Customers may need to customize 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.

Please contact Mobileforce Support to create a layout specific to your business needs. 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 scheduling and dispatching as well as routing
for a customer. The Schedule & Dispatch screen allows one to add custom
global actions buttons to the top right of the screen, such as "Plug Route", "Smart Route", "Auto Schedule", and "Map Appointments".
This is done via Application Level Properties. Please contact Mobileforce Support to help implement custom global actions for Scheduling and Routing, that address your specific business needs.

Field Service Application Level Properties

The table below lists all supported Field Service properties. Please contact Mobileforce Support for customization of these properties for your needs.

Offline Access Properties

The folllowing properties control the offline capabilities of the Mobileforce Mobile App.

• offline-enable Enable offline access in Mobile App
• offline-sync-tables Specify a list of tables that need to be sync-ed for offline access.

For example,

  <prop key="offline-sync-tables">OfflineQuote,OfflineQuoteLineItem,OrderPadBookPrice,OrderPadCSP,OrderPadCustomers,OrderPadLastPriceZLST,OrderPadLastPriceZSSP,OrderPadProducts,OrderPadRangePrice</prop>

• offline-sync-up-to-date-tables Specific tables from the mobile app that are to be sync-ed back with the backend when the device goes back online.

For example,

    <prop key="offline-sync-up-to-date-tables">OfflineQuote,OfflineQuoteLineItem</prop>

• offline-cache-sqlite whether (or not) to cache offline data in a sqlite table.

For example,

   <prop key="offline-cache-sqlite">1</prop>