00171309

063590

In the ServiceMax Go App for Windows, output documents failed to reflect the Salesforce user’s locale setting of English (Hong Kong SAR China). When the user generated a service report for work order, the date format incorrectly displayed as MM/DD/YYYY instead of the expected DD/MM/YYYY. This issue occurred because the moment library used in the application did not support the specified locale.

12.0.0

00168606

063057

In the Windows version of the ServiceMax Go App, the Join/Create WO-... Group functionality did not initiate a work order-specific Zinc conversation. When the user logged in, selected a work order without an existing Zinc conversation, and clicked the option to create or join a group, the app reverted to Zinc but displayed a blank messaging screen without any reference to the work order. This occurred despite the SVMX-Zinc integration being active between the Salesforce instance and the Zinc organization.

12.0.0

00164460

061771

The forced configuration sync was not enforced across all user devices, including Windows, iPad, and iPhone. When a force config sync was initiated, some devices did not trigger the sync process. This occurred because the sync reminder only started after the app received a notification, and in cases where the notification was not received, the force config sync did not activate.

12.0.0

00163107

061394

Managed Windows PCs did not receive device notifications, which caused the configuration sync to fail in the ServiceMax Go app. The issue was linked to notifications either being delayed or not appearing in the Windows Notification Center. Sometimes users had to manually refresh to see notifications. Additionally, even when notifications appeared within the app, the expected Windows Toast notifications, including banners and sounds, did not trigger at the device level.

12.0.0

00169855

063235

When a work order with travel duration spanning two calendar days was rescheduled using drag and drop on the calendar, the End Date Time field updated incorrectly. This issue occurred because the drag and drop functionality did not support multi-day events, and travel time events were mistakenly not excluded from this unsupported behavior.

11.4.0

00168604

062872

Technicians observed that images in the Action Plan Summary rich text field appeared reduced in size after clicking more on the case details page. The problem occurred because the Image component in React Native could not read the image's size when the image path was passed, defaulting on the size to 100x100.

11.4.0

00166845

062345

The output documents did not reflect the locale settings configured for the Salesforce user. This issue occurred because the Moment library did not support the en-de locale for English (Germany). As a result, the system defaulted to the en-US format instead, leading to incorrect localization in the generated documents.

11.2.0

00165926

062105

In the output document, number-type checklist questions did not display data when the value was 0. This occurred because, in the current implementation, the number field with a value of 0 was treated as a false value, causing it to be excluded from the output checklist in OPDOC.

11.2.0

00162763

061238

Windows notifications intended for the previously logged-in user were also sent to the current user. These notifications were not visible on the Go app's Notifications page.

11.1.0