Release notes icon Release Notes

You can use the links below to access release notes for various FieldFX packages and modules.

For more information:

FieldFX Releases

This table details the various FieldFX Modules or Managed Packages with a description of each and when it was last upgraded:

FieldFX Module or
Managed Package
Description Last Upgraded

With the Admin Portal, system administrators can access user-friendly screens to manage various aspects of the FieldFX system.

You can access functions such as user access, workflows, price book rules, and FX Logs viewers and Sync Events Viewers. These updates contain changes to the various tools you can find in the Admin Portal.

See Admin Portal Updates for
individual tool versions.

The FieldFX Base Package contains the core FieldFX components.

You must install the FieldFX Base Package to use FieldFX and any combination of its modules.

Current
Version

1.575

Previous
version

1.569.2

See Push Upgrades for the push upgrade schedule.

FieldFX Lightning Components are available through the FieldFX Lightning Managed Package, You can use the FXL Components in FieldFX Back Office when using Lightning Experience.

To use the FieldFX Lightning package starting with version 1.225, you must use the FieldFX Managed Package version 1.529 or higher.

Current Version

1.246

Previous Version

1.243

See Push Upgrades for Push Upgrade schedule.

FieldFX Mobile is a HTML5 app accessible through a web browser or the FieldFX Windows Client. FieldFX Mobile Pro is a mobile device app for accessing FieldFX Mobile mobile devices. These updates are for FieldFX Mobile.

Release
Channel
Version Date Pushed

Sync V4 Beta

Current Version
4.0.1.4881

5/7/24

Sync V4

Current Version
4.0.1.4881

5/7/24

Sync v4 Quarterly Beta

Current Version
4.0.1.4881

5/9/24

Sync v4 Quarterly

Current Version
4.0.1.4881

5/18/24

FieldFX Module or
FieldFX Managed Package

Description

Last Upgraded

The FX Timecards module is a time management solution that makes it easier to track payable time for field employees. You can track time off requests and collect Time cards in to a payable timesheet.

Field users can enter cards using the FX Timecards app, available for iOS and Android devices.

Version Date Pushed

Current Version
MP 1.39

8/12/22

Current Version
iOS 1.2 /
Android 1.28

The Packet Viewer is a tool in the Audit Log that displays the contents of sync packets.

Version Date Pushed

Current Version
87

8/19/20

Use the Report Viewer to run FX Reports and attach them to records.

Release
Channel
Version Date Pushed

Beta

Current Version
256

5/23/23

Latest

230

Deprecated

230

The FX DataGuide module was previously used in FieldFX. It has since been deprecated and now FieldFX uses the same DataGuide package that ServiceMax has developed and uses in their software.

The FX Schedule & Dispatch is an integrated resource management solution that allows you to manage your field operations more efficiently.

Version Date Pushed

Current Version
511

5/20/24
(PROD)

507

6/20/23
(BETA)

FieldFX Module or
FieldFX Managed Package

Description

Last Upgraded

Deprecated Items (No longer supported)

For more information, see FieldFX Deprecated List.

Push Upgrade

We generally release new version of the FieldFX Base Managed Package and FieldFX Lightning Managed Package once per month.

Four times each year, we push upgrade the Lightning Managed Package and the FieldFX Base Managed Package release to Sandbox orgs.

Two months after pushing the FieldFX Base Managed Package and Lightning Managed Package to Sandbox orgs, a push upgrade is performed to Production orgs.

For specific release date by Salesforce Instance see the Push Upgrades.

The version pushed to Production orgs is the package pushed to Sandbox orgs or a later version. The version addresses any defects identified during the Sandbox testing period.

Push Upgrades occur at the same time as push upgrades for the FieldFX Base Managed Package. To upgrade to an available release between push upgrades, contact Support.

FieldFX Impacts from Salesforce Releases

Summer '23

Update Name Update Summary FieldFX Impact

With this update, Salesforce no longer a requires a user running a flow to have explicit access to Apex classes for the same flow.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Disable Rules for Enforcing Explicit Access to Apex Classes, follow the activation steps.

With this update, you can shield your org and network from malicious attacks with content sniffing protection. This change helps prevent the browser from loading scripts disguised as other file types when your users access external content and websites from Salesforce.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Enable Content Sniffing Protection, follow the activation steps.

This update enforces the generation of a different cross-site request forgery (CSRF) token for each Lightning app, which ensures that a token is used only in its intended context. The update also improves the handling for invalid and expired tokens. This update was first available in Spring ’23 and is enforced in Summer ’23.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Security Enhancements for CSRF Tokens for Lightning Apps, follow the activation steps.

To improve security, this update prevents flow interviews from resolving the $Api.Session_ID variable at run time. Previously, when a flow screen included the $Api.Session_ID variable, the browser session ID of the user that ran the flow appeared on the screen. A user was able to employ the session ID to bypass security controls.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Disable Access to Session IDs in Flows, follow the activation steps.

The Visualforce Remoting API uses JavaScript to directly call methods in Apex controllers from Visualforce pages. To prevent unauthorized serialization and deserialization across packaging namespaces, this update validates the JsonAccess annotation of your Apex classes.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Enable JsonAccess Annotation Validation for the Visual force JavaScript Remoting API, follow the activation steps.

To conduct business wherever you are, adopt the International Components for Unicode (ICU) locale formats. Locales control the formats for dates, times, currencies, addresses, names, and numeric values. ICU sets the international standard for these formats.

  1. Access your Back Office Setup.

  2. In the Quick Find box, enter Release Updates.

    The Needs Action tab shows all the updates that are needed to your org.

  3. For Enable ICU Locale Formats, follow the activation steps.

When this update is enabled, regardless of API version, REST response headers defined in Apex via the RestResponse.addHeader(name, value) method have the header names validated based on RFC 7230.

In a browser window:

  1. Go to https://status.salesforce.com

  2. Under Trust Components, click Go to Status.

  3. In the Search field, enter you org instance.

    To find your org ID and instance number, see Find your Salesforce Organization ID.

  4. To check if a major release upgrade is available for your org, click the Maintenance tab.

    Before activating this update, check with your package providers to make sure all your installed packages are compatible.

Update Name

Update Summary

FieldFX Impact

Winter '22

My Domain Activation Required

  • Beginning with the Winter '22 release, Salesforce requires that all orgs activate a My Domain.

  • My Domain impacts the URLs that display when navigating FieldFX Back Office.

  • Switching to a custom My Domain reduces potential impacts when Salesforce switches an org to a different Salesforce instance.

  • My Domains have no impact on the operation of FieldFX or any of its modules, but all orgs without a My Domain defined should follow Salesforce’s procedures for activating a My Domain, including thoroughly testing any custom code and integrations in a Sandbox before activating in Production.

  • Be aware of My Domain considerations detailed by Salesforce.

The following orgs already have My Domain enabled:

  • Orgs running FieldFX Lightning

  • Orgs using single sign-on

  • Production orgs created on or after the Winter '21 release

Visualforce Remoting Changes

  • Salesforce is enforcing tighter security for the ways Visualforce pages use Apex controllers.

  • FieldFX by ServiceMax, Inc. has completed testing with the setting enabled and found no impacts.

  • For details and testing instructions, see the Salesforce help article on the updated requirements.

Summer '22

End of life for legacy API versions

What is Changing? What is FieldFX doing to prepare for this change? What do I need to do to prepare for this change?

As of the Summer ’22 release, legacy versions 21.0 through 30.0 of the Salesforce Platform API are no longer supported by Salesforce. Calls continue to work, but Salesforce no longer provides any assistance if problems arise. For more information, see Salesforce Help: Salesforce Platform API Versions 21.0 through 30.0 Retirement

Beginning with the Summer '22 release, the API calls to those versions will no longer work.

We have reviewed the FieldFX products and found no impacts from this change.

Review any custom code and make sure all services that rely on the Salesforce endpoints use an API version greater than 21.0. Complete the assessment and any required updates prior to the upgrade to Summer '22 in May 2022.

Spring '22

International Components for Unicode (ICU) Locale Formats

What is Changing? What is FieldFX doing to prepare for this change? What do I need to do to prepare for this change?

Beginning with the Winter '20 release, Salesforce added a new international locale standard to supplement and eventually replace the previously used Java Development Kit locales.

With the Spring '22 Salesforce release, all orgs will be required to use the International Components for Unicode (ICU) locales.

Orgs created after the Winter '20 release had ICU locales enabled by default when the org was created. However, the option may have been disabled.

Orgs created prior to the Winter '20 release did not have this option, and Salesforce has not required orgs to enable it. This changes with the Spring '22 release when the use of ICU locales is required.

For more information, see How are locale settings affected?

We have tested the impact of enabling the ICU locales to the FieldFX suite of products. Our testing did not uncover any conflicts with FieldFX packages.

Salesforce has a document that summarizes the steps to take to switch from using the JDK locales to enabling ICU locales instead.

Familiarize yourself with the steps that are required and be ready to complete testing on custom code and other apps you may have installed.

How are locale settings affected?

Locale settings effect the formats used for elements such as dates, times, numbers, and currencies.

Salesforce has a help document that shows the differences between the current Oracle JDK locales and the new ICU locales.

For US English, the differences include:

  • Datetime formats add a comma between the year and the time

  • Negative currencies switch from using parentheses to a negative sign at the beginning of the amount

    Screenshot of en-us differences

Refer to the document linked above for the differences in formats for other locales, which may have additional impacts beyond dates and currencies.

Summer '21

The Summer '21 Release begins rolling to Sandboxes on April 4, 2021. See Salesforce’s Trust Status page to determine when your org(s) update to Summer '21.

Apex Property Restrictions

Restriction of Apex Controller Methods for Aura Components in Managed Packages

  • Beginning with the Summer '21 release, Salesforce is enforcing an update first introduced in the Summer '17 release.

  • The update enforces a rule on Apex methods that requires methods calling Aura components outside of the package namespace to have a global access modifier. Previously, Aura components outside of a namespace could access non-global methods.

  • See the Salesforce notice.

Access Modifiers on Apex Properties in Lightning Component Markup

  • With this release, Lightning Components are bound by the same access restrictions as other Apex properties.

    For example, a Lightning Component’s markup can no longer access Apex properties marked with an access of private or protected.

  • See the Salesforce notice.

Impacts to FieldFX

  • FieldFX has tested the impacts of these newly enforced restrictions.

    Aura components and Lightning Components have passed our tests.

Security Announcement - March 31, 2021

  • During a routine security review, Salesforce identified a vulnerability in a Salesforce AppExchange package called Lightning Sharing.

  • The package could allow users access to the org’s sharing permissions.

  • As a result of the vulnerability, Salesforce has removed the package from the AppExchange.

  • The package is no longer required, as a similar functionality was added for all orgs in the Spring '21 Salesforce release.

  • Orgs with the Lightning Sharing package installed should remove the package and use Salesforce’s sharing settings instead.