00171483

063680

The ServiceMax Go app stopped responding when users added multiple items using +Add Parts Request Lines in the Parts Request Lines tab during online search, which caused a performance lag.

13.0.0

00174822

064604

On iOS, the ServiceMax Go app crashed when users tap the Submit button in the DataGuide form on the Site Safety Checklist screen while screen mirroring was enabled, which affected task detail, task list, checklist, image compression, location history, app reset, and email functionalities.

13.0.0

00170547

064757

Events did not appear in the Calendar when a Work Order was created through Account Search > Actions > SFM – Work Order from Account > Event in Child, due to a screen refresh issue where the event existed in the local database but did not render until the app was closed and reopened.

13.0.0

00175399

064771

The wizard order configured in Service Flow Manager > Wizards for the Procedure object was not reflected correctly in the Go app. When users opened a Work Order and accessed a Procedure under Actions, the sequence of steps did not match the order set using Reorder Wizards, even though it displayed correctly in the Lightning web interface.

13.0.0

00174992

064870

The Appointment view did not open the customer contact information hyperlink on Pixel 7 devices, and the phone app did not launch when users tapped the link, even though the hyperlink opened correctly on Pixel 9.

13.0.0

00177449

065593

The iOS photo picker UI displayed in German instead of Dutch when launched through Select Images & Videos for Backoffice > Add Image or Video > Choose from Camera Roll on a specific iPad OS and app version combination, which caused the SFM photo picker to default to the device’s secondary language instead of the primary language.

13.0.0

00177711

065508

In the Go app version 12.2.0, users with their language set to Arabic, experienced a UI rendering issue where the SFM screen displayed a large empty white space at the top. This pushed the header and all content far down the page, requiring excessive scrolling to view or interact with fields. The problem occurred due to missing centralized right-to-left (RTL) handling in the app’s popover layout logic.

12.4.0

00175106

064817

The updated record disappeared from the list after saving when technicians edited a part line in the Work Detail section through a linked SFM within the Debrief process. This occurred because the qualifying criteria (QC) for the section used CURRENTUSERRECORD literals, which were not correctly replaced with actual values when the linked SFM closed and the QC was reapplied. As a result, the updated record was incorrectly excluded from the displayed list, causing it to vanish from view.

12.4.0

00174958

064676

Technicians using the Go app on iPads experienced an intermittent issue where the start date and time pop-up window in the labor entry section became unresponsive or failed to close. The problem occurred when users repeatedly tapped the date-time picker fields, causing the popover’s display state to become unsynchronized with its animation timing. As a result, the pop-up sometimes remained visible and unresponsive, preventing users from proceeding. This behavior was linked to timing conflicts in the display and hide logic of the date-time picker when combined with custom JavaScript configured for the onChange event.

12.4.0

00175738

064905

On Android devices, when users opened and shared documents from the Go app, the file names did not display as expected. Instead of showing the configured naming convention with work order details, the documents appeared with a system-generated ID. This issue was specific to Android, as iOS displayed the correct file names, and it stemmed from stricter file handling rules in the Android system.

12.3.1

00169918

063503

Users on Samsung S25 Ultra devices running Android 15 experienced significant lag in the Go app. The issue appeared intermittently during common actions such as filling out checklists, using the back button, or opening work orders from the calendar.

12.3.1

NA

NA

On iOS 26 devices, the Go app crashed when users tapped Take Photo or Take Video while attempting to attach media in the Image and Video section. The crash occurred consistently during the process of adding attachments by capturing photos or videos directly from within the app.

12.3.0

00176905

065158

Users were unable to log in to the Go app because the sync process failed with the error message The app cannot access the configuration for this user. This prevented access to the application and blocked normal usage.

12.3.0

00176713

00176716

00176908

00176715

00176719

00176907

00175424

064829

Deeplinks configured to run in sequence did not function correctly. When multiple deeplinks were chained, only the last one in the sequence executed, while the earlier deeplinks were ignored. For example, if two deeplinks were set up, only the second worked, and if four were configured, only the fourth executed. This caused incomplete navigation flows where the expected series of linked actions did not occur.

12.3.0

00175655

00171274

063587

In the Go app, when users initiated an inventory transfer and repeatedly tapped the Send button, multiple transfer requests were created instead of just one. The issue occurred because the app did not disable or block the button while the first request was processing and lacked a debounce mechanism to prevent rapid multiple taps. As a result, duplicate requests were submitted whenever users clicked the button more than once.

12.3.0

00176179

064995

In the Go app, partner portal users experienced failures when attempting to open checklists from the wizard. Checklists with more than 30 questions did not load properly, causing the app to hang and become unresponsive. Users were forced to kill and relaunch the app to continue working, as the checklists never displayed.

12.2.0

00175958

00175980

00174592

064577

In the Go app, when users opened the Manage File Exclusion Mobile MAS and selected the Exclude File checkbox deeplink, the change did not persist after saving and relaunching the report. The checkbox appeared unchecked even though it had been selected. The issue only occurred when saving from the Go app; if the selection was saved from the browser, it was correctly reflected in the app.

12.2.0

00170357

063832

In the Go app, technicians could not access the Edit/Debrief Work Order step in the Field Service Management wizard, as it appeared greyed out even though it was visible and accessible on the web. The issue occurred because the wizard step criteria used Owner Id = SVMX.CURRENTUSERRECORD.Id, which did not evaluate correctly in the mobile app. When this condition was removed, the step became enabled and functioned as expected.

12.2.0

00170816

063561

On iOS devices, when technicians could not download the updated MAS package when they reset the Go app causing inconsistent and unexpected behavior.

12.2.0

00174128

064574

The output document did not print properly when users previewed or finalized the estimate report for work order in the Go iPad app. After navigating to work order search > My PPM work orders, downloading the record, and clicking Preview of estimate report, the document rendered incorrectly in both the preview window and the final output. It was traced to an RN upgrade when a runtime formula in the customer’s template failed, the logic no longer fell back to legacy mode and the report rendered only once and improperly.

12.1.2

00174071

064473

After switching their iPad or iPhone region to the Netherlands, users opened work order in the Go app version 12.0, navigated to the Debrief section’s Travel Time, and entered a decimal value, for example, 0,25, in the line Qty field. Upon saving, the app consistently reformatted the input as 25.0000, demonstrating a failure to preserve the locale-specific decimal notation across both sandbox and production environments.

12.1.2

00174439

00174431

00174085

064397

In the Go app version 12.0.0, when users switched to the weekly calendar view and opened a day’s popover, the list of work orders exceeded the initial viewport and forced them to scroll before they could select and open a work order, a behavior that had not occurred in earlier versions.

12.1.2

00174291

00171274

063587

During the Inventory Transfer process in the Go app, technicians initiated a request and clicked the Send button multiple times before the initial submission completed. Because the Send button remained enabled and no warning appeared after the first click, each subsequent click generated a new transfer request, resulting in duplicate requests instead of a single, consolidated submission.

12.1.2

00167053

062804

Users attempted to unlink a change order line from its associated work order by clearing the work order number field and saving in the Go app, but the number remained on the record. This occurred because the .pickBy utility function that compared initial and updated child values filtered out entries set to null, so the cleared field wasn’t detected as modified. As a result, the system never committed the removal, and the original work order reference persisted.

12.1.2

00174087

064400

The issue occurred during the customer service report (CSR) generation on Windows. Instead of rendering formatted content, the CSR included raw HTML markup. This regression surfaced because an upgrade to the Cheerio HTML-parsing library changed its handling of markup, allowing HTML tags to pass through unprocessed into the final report.

12.1.1

00174086

064399

When technicians completed a checklist and triggered a smart sync, the process failed with a conflict error because the payload included a full object in a reference field instead of its ID. The server responded with an Unable to parse the conflict error msg JSON indicating it could not deserialize the reference from a START_OBJECT value. This malformed reference payload prevented the sync from completing as it had in previous versions.

12.1.1

00174244

064396

In the Go app, technicians logged in, started travel, completed the pre-job checklist, clicked Start Work, and saved the record, but the travel line items failed to update their end date/time and status as part of source object update, those fields remained blank despite updating correctly in earlier versions.

12.1.1

00174103

00174068

064383

Technicians attempted to complete a work order using the Work Complete screen, but each save action failed with a There was a problem while running custom script error. This defect emerged after upgrading to Go app version 12.0.0 whenever any SFM code snippet contained an async function, whether on load or before save.

12.1.1

00174280

064413

Technicians assigned to a work order attempted to complete or reopen it using the PCR Code Entry FT screen, but the interface froze each time they searched for a product in the lookup while entering the PCR code. This freeze began occurring after the ServiceMax 12.0 upgrade and forced technicians to reset the app and re-enter the PCR status, often twice, to proceed. Despite multiple reset attempts and correct data downloads, the screen continued to lock up unpredictably, preventing completion of the work order actions.

Also, the Go app began unexpectedly reloading certain screens while technicians were actively entering data, most notably on the Edit SFM form and during OPDoc signature capture. These untimely syncs interrupted user input and risked data loss, as the refresh logic did not account for in-progress edits or signature actions after the version 12.0.0 architectural changes.

12.1.0

00174227

00174238

00174130