FieldFX Mobile 2020 Updates

FieldFX Mobile users can now interact with FX EAM Task Labor records.

Depending on permissions, users can

User permissions and compact layouts determine what is available to the user on this screen.See the Configuration Help for details.

FieldFX Mobile users with access to FX EAM can now view Inventory Transactions that have issued to a Work Order.

Users with the ability to add inventory transactions can create them in FieldFX Mobile.

FX EAM Inventory Transactions cannot be modified in FieldFX Mobile.

See more in the Inventory Transactions page and the Inventory Transactions Details page.

The syncing of attachments can tremendously impact sync times.

A new custom setting allows for orgs to opt out of syncing attachments to mobile devices.

When the custom settings is enabled (is set to True), the attachment portion of the sync process is skipped.

Use the following steps to add the Custom Setting and enable it to opt out of attachment syncing in your org:

We have added new custom permissions that allow you to hide tabs from users who do not need access.

The new custom permissions are:

Add any of the custom permissions to the Profile or Permission Set for the user to prevent the tab from displaying to the user in FX Mobile.

Bringing parity with the other FX Mobile screens, FX EAM Work Orders now display a work order’s Tracking ID to aid in navigation through the FX Mobile Work Order screens.

Select a breadcrumb item to navigate back up through screens

FX Mobile now honors the formula setting of Treat blank fields as blanks.

Number, currency, and percentage fields can now be seen as blank in FX Mobile.

FX EAM Work Tasks for a Work Order now display in a grid view.

Fields display from the Work Task object’s Compact Page Layout.

Editable fields can be modified directly on the grid list.

Users can use Bulk Edit to make changes to multiple tasks at the same time.

The sum report helper works by first rounding each value to sum, then calculating the result.

This release adds a new setting to the sum helper, roundEach. Add this setting and set it to False to change the default behavior to wait to retain the full precision of each value and only perform rounding on the result.

{{sum items "Total_Hours__c" precision="1" separator="," decimal="." roundEach="false" }}

A new dialog displays if a user attempts to close a report when unsaved changes exist, such as a customer signature.

The message informs the user that unsaved changes will be lost and gives the user an opportunity to return to the report to save changes.

PDF file attachments added to records in back office via the Files API or Chatter Attachments can now be viewed on mobile devices within FieldFX from the Files tab.

Previously, users received a message that the document could not be displayed.

Users can now choose to expand or collapse bundled items when viewing Quote Items and Ticket Items.

Page loading and scrolling adapts as expected and loads properly whether bundles are expanded or collapsed.

When a user creates a new Quote or Ticket in mobile in an org with multicurrency enabled, the currency for the new record is set to the same currency as the Price Book’s currency.

Previously, the user’s default currency was used.

Users with access to FX EAM can now interact with Work Orders, Work Tasks, and Work Task Steps from a mobile device. The functionality of these screens is similar to Back Office.

See the Mobile Configuration Help instructions for details about setup options.

See the Getting Started pages for FX EAM Mobile for instructions on using the screens.

We have improved sync performance for customers using the FX CPQ module.

Administrators can now specify objects that users have access to in Back Office but are not needed in Mobile. Specified objects do not sync to the mobile device, but remain available for the user to access in Back Office.

Fields can be removed from the mobile Bulk Edit screen.

Add any Ticket Item fields that should not be bulk edited to the FX_Ticket_Item_Bulk_Edit_Exclusion field set.

To add the fields:

After navigating to the Reports tab, we now wrap report names so that the entire report name displays in the list. This helps users identify the desired report more quickly, especially when multiple reports share a similar name. Previously, the report name was limited to one line of text and longer report names were truncated with an ellipsis (…​) at the end.

We have made improvements when working with Ticket Items, such as adding, deleting, copying, sorting, or updating records. (9687)

When a grid contains calculated fields, we improved the load times when switching between record type views. (9718)

When the grid contains bundled items, we improved the load times and performance when expanding or collapsing the bundled items and when applying or switching record type view filters to the grid. (9737)

We continuously work to improve the end user experience of the FieldFX Mobile application.

This enhancement reduces memory usage, creating a faster and more responsive interface. Users see the performance improvements when:

When a field user captures a signature, FieldFX now records the time stamp of a signature and stores the most recent time stamp to the ticket records.

If the FX5__ReportSigned__c field does not exist, no time stamp record is stored.

FieldFX records the last signature captured for any record that is part of the Ticket.

When a field user captures a stamp, FieldFX now records the time stamp of the stamp and stores the most recent time stamp to the ticket record.

If the FX5__StampCaptured__c field does not exist, no time stamp record is stored.

FieldFX records the last date and time a stamp is captured across any record that is part of the Ticket.

We have added a new Pending File Attachments section to the Sync screen to track Attachments created in mobile.

Attachments for new Jobs and Tickets created in the mobile app display in the Pending File Attachments section.

Images added to reports as attachments display in the Pending File Attachments section.

Update Cleared status flag after a sync successfully processes

Track success or failure of syncs with the Originating Audit Log and New Audit Log fields on connected entries