• The user must be online (internet connectivity) to be able to receive notifications.

• To receive notifications for updates done by a dispatcher or a service manager, you can add their profile to the connected app. This avoids notifications sent for updates done by other users.

• Do not use formula fields in SFM Expressions of the Filter criteria that evaluate the "Mobile logged in user". For example, FSR_Name. SVMXC__Salesforce_User__r.Id = $User.Id. Since these expressions are run on Salesforce, the expression may evaluate to false as it has no context of the mobile user.

• Ensure the SFM chosen in the SFA configuration is available to the technician. If the SFM chosen in the SFA configuration is not available to the technician, then:

◦ For Work Orders and custom objects, the default view SFM is displayed.

◦ For Events, the Appointment screen is displayed.

• Updates made to a field via Salesforce Workflow rule or Salesforce Process Builder do not trigger a Push Notification in SFA.

• Push notifications are sent to only those recipients belonging to the group profile selected in the Service Flow Automation configuration.

• In the fieldset configuration section for Salesforce and ServiceMax object add the fields to the required field option to trigger the notification in the app for any updates in that field.

• SFA notifications do not work when multiple records are created or updated in the same transaction as the SFA is initiated only once per transaction (apex execution). If multiple records of the same object are created or updated in the same transaction, only the first created or updated record triggers the SFA notification.

• For custom implementation such as Flow, or Apex Trigger where a record is created or updated from a Record-Triggered Flow and expect to send a push notification based on this update, you must optimize the flow using the option Fast Field Updates, which runs before the record is saved to the database.