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.

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.

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.

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.

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.