Skip to main content
Solved

FSM mobile sync

D
Sidekick (Customer)
Forum|alt.badge.img+9

Hi All,

 

I have some issues with getting the updated data in mobile.

I created a additional filter in the Mobile Task Overview, for tasks with status Waiting. That all works fine. If update a task via the web or smart client, it will just pop up in the list, all good.

The issue occurs when a user changes a task to the status Waiting task via a custom Mobile button (which has a custom client script to update the task), the task will be updated correctly in the backend (aslo correct in the web and smart client). But won’t popup in the mobile, only after I manually update someting in the task (like updating the description) in the web or smart client, then it will popup in mobile after a few seconds just fine.

I tried setControlValue and the generateDataTransaction function, all updating the task just fine, but won’t update/sync the task in mobile.

Now as a workaround I created a Business Rule which will be triggerd when status changes to waitng, which sends an XML update to the task (see below). And then the task will popup just fine. Seems like a xml will trigger the sync or something, but this seems like a dirty solution for now.

<update_task>
 <task>
  <task_id>@TASK_ID</task_id>
  <update/>
 </task>
</update_task>

 

Any toughts?

Best answer by drooij

Thanks all for your suggestions. It seems that the functionality is working fine, but.. It works fine only for recent created or updated tasks. When I use an old task only the second update will trigger the sync to mobile somehow.. Not sure why or how

View original
Did this topic help you find an answer to your question?

Shneor Cheshin
Superhero (Employee)
Forum|alt.badge.img+28

Hey @drooij 

Have you updated the sync rules?

You need to add the new status to the sync rule. Both ‘Initial Query’ and ‘Related Query’.

The condition will be something like below

        <constraint>
          <left_operand>task.task_status</left_operand>
          <operator>eq</operator>
          <right_operand>WAITING</right_operand>
        </constraint>

Add it with <or /> to other task_statuses already in the sync rule.

Cheers!

D
Sidekick (Customer)
Forum|alt.badge.img+9
  • drooij
  • Sidekick (Customer)
  • August 25, 2022

Hi @Shneor Cheshin, thanks. I indeed added the waiting status to the sync rule. But still same issue. Still have to do a manually update on the task, or use the business rule which sends the xml.

Lee Pinchbeck
Ultimate Hero
Forum|alt.badge.img+24

Hi @drooij,

Sounds like the extract for the table is not being triggered by the mobile update. Can you check the extract to see what the settings are? It may be that this is by design though, to prevent looping with mobile updates. Does the mobile update if other information is changed or just the status?

Kind regards,

Lee Pinchbeck

Currently reading: The Way of Kings - Brandon Sanderson
brian.gummin
Hero (Employee)
Forum|alt.badge.img+15

I recommend checking the mobile database.  Pause Sync and execute your custom button.  On the Query screen: select task_status from task where task_id = nnnn.  If the status isn’t WAITING, then your client script is wrong.

D
Sidekick (Customer)
Forum|alt.badge.img+9
  • drooij
  • Sidekick (Customer)
  • August 31, 2022

Thanks all for your suggestions. It seems that the functionality is working fine, but.. It works fine only for recent created or updated tasks. When I use an old task only the second update will trigger the sync to mobile somehow.. Not sure why or how

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings