Skip to main content

Hi Team, 

 

I am trying to configure App Param "RECEIVED_TASK_EVENT" but I can not see the task.last_received_person_id or task.last_received_dttm consistently set.

The app param description is as follow,

“The Event Type used to determine if a Task has already been received on a mobile device. When populated, a Task Event Generation business rule must be configured to create this task event when LAST_RECEIVED_PERSON_ID changes from empty to populated.”

Need to understand how the baseline code is setting last_received_person_id, and last_received_dttm when the mobile user has "received" the task? how can I configure RECEIVED_TASK_EVENT app param? and what are the possible Param Values that can have?

Thank you in advance for your help on this.

 

Regards,

Wickram B.

 

Hi @wickrambug,

The fields should be populated when the mobile device syncs back a confirmation of receiving the sent Task, it is part of that confirmation sync message. If this is not occurring consistently this may be due to signal issues on the mobile or a large sync queue that the system needs to clear. 

Before you can set the app param you need to make sure the Business Rule to create the event entry based off of these fields being set is correctly set up. You can choose any value for the event type from the created event types in the code table event_type. If a suitable one does not exist you can first create it in the code table. It will then appear for selection in the Business Rule.

Once the Business Rule is set the app param then needs to be set to have the same event type as the Business Rule.

Hope this helps,

Lee Pinchbeck

Hi @wickrambug,

The fields should be populated when the mobile device syncs back a confirmation of receiving the sent Task, it is part of that confirmation sync message. If this is not occurring consistently this may be due to signal issues on the mobile or a large sync queue that the system needs to clear. 

Before you can set the app param you need to make sure the Business Rule to create the event entry based off of these fields being set is correctly set up. You can choose any value for the event type from the created event types in the code table event_type. If a suitable one does not exist you can first create it in the code table. It will then appear for selection in the Business Rule.

Once the Business Rule is set the app param then needs to be set to have the same event type as the Business Rule.

Hope this helps,

Lee Pinchbeck

Hi @Lee Pinchbeck,

Thank you for your answer.

You mentioned, “a large sync queue that the system needs to clear”. Is there a way to overcome this scenario? 

Hi @wickrambug,

You would first need to look at the data to determine why it is so large e.g. are there errors blocking the sync, is the build up on the device on in the mm_message_out queue on the server, are there a large number of entries for the same table?

From what I have seen it is usually either that a large update has been done to a table that has flooded the queue and needs time to clear down or an inefficiency in the sync rules where the rule could be further filtered or fields excluded or could be set to run less frequently. It could also be that the mobile user is not keeping their device active for long enough for the message to be sent through.

Kind regards,

Lee Pinchbeck

Hi @wickrambug,

You would first need to look at the data to determine why it is so large e.g. are there errors blocking the sync, is the build up on the device on in the mm_message_out queue on the server, are there a large number of entries for the same table?

From what I have seen it is usually either that a large update has been done to a table that has flooded the queue and needs time to clear down or an inefficiency in the sync rules where the rule could be further filtered or fields excluded or could be set to run less frequently. It could also be that the mobile user is not keeping their device active for long enough for the message to be sent through.

Kind regards,

Lee Pinchbeck

Crystal. Thank you for the clarifications @Lee Pinchbeck 

Reply


Terms & ConditionsCookie settings