Best Practice for Enforcing Single-Device Usage in FSM Mobile

Hi Vaibhav,

1. No, there isn’t an application parameter available for this.
2. No, but you can make use of the application parameter DEVICE_LAST_SYNC_LIMIT.
   
   Description:
   Determines whether the person_mobile.last_sync_dttm is less than the current date minus the value of the DEVICE_LAST_SYNC_LIMIT param. If it is, mm_message_out records are deleted and the affected device is automatically deactivated.
    
3. This is the intended application design. You can use the parameter mentioned at #2 to manage devices and mm_message_out growth. Further, you can get an overview of all active devices and their last sync date in the Mobile Dashboard, which is available in Smart Client.

Best regards
Roman

Hi Roman,

Thanks for sharing your points.

As per your suggestion, I have created a query that identifies all mobile devices whose last sync time is older than the configured synchronization threshold. This helps us identify devices that are out of compliance with the expected sync window.

Parameter details:

• Param Name: DEVICE_LAST_SYNC_LIMIT

• Param Value: 3 (days)

SELECT pm.person_id,
       pm.device_id,
       pm.client_version,
       pm.os_type,
       pm.os_version,
       pm.last_sync_dttm
FROM person_mobile pm
WHERE pm.last_sync_dttm < SYSDATE - (
    SELECT MAX(TO_NUMBER(param_value))
    FROM metrix_app_params
    WHERE param_name = 'DEVICE_LAST_SYNC_LIMIT'
);

However, I have an additional concern and would appreciate your guidance.

We currently have an alert notification when the MM message user count exceeds 3000 for a particular user. In such cases, we ask the user to manually sync the device, as a large backlog may cause slowness during mobile synchronization.

From an operational perspective, we would like to understand whether there is any supported way to trigger or enforce a device sync from the backend, without requiring the user to manually initiate the sync from the mobile application.

Could you please clarify whether:

• Backend-initiated device synchronization is technically supported, or

• Manual user action is mandatory due to mobile client design and security constraints?

Your clarification will help us set the right operational expectations and design the appropriate handling mechanism.

Thanks in advance for your support.

Hi Vaibhav,

you can use the Mobile Dashboard in the Smart Client to perform a device initialization or refresh of specific tables. You can also refer to the attached FSM Mobile Guide (p. 51) for more details.

Further, you can use background sync but this requires configuring of Azure Notification Hub. However, that only works when the app is opened in the background. More details about this feature can be found in the attached FSM Mobile Messaging Guide (p. 13).

Hope that helps!

Best regards
Roman