Task list inconsistency

mikej117 over 8 years ago

For the applications that we have built, we get an occasional issue where the task list is inconsistent with the following expected state: a user has just completed and submitted/rejected a task, then the next page that appears is the user's task list, which contains the task that was just completed.
Today, one of our testers managed to reproduce this scenario several times. At one stage, the Tasks link in Tempo showed that there was no tasks (no number shown inside brackets next to the 'Tasks' heading/link), but then a task appeared on that page.

Is there anything that can be done to stop this inconsistency from occurring?
(It seems to be caused by Tempo reading the task list information before it's been updated by the process execution engine.)

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 8 years ago

There might be a short lag as you mention. Does it get better if you activity chain the task to the end node?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sally Mason
Appian Employee
over 8 years ago

The number of Tasks in the Tempo menu bar is only refreshed/recalculated when the page is reloaded, or the User navigates to another page in Tempo, the number of Tasks may not reflect the actual number if the User is still completing a flow within the one page. Is this what the User in your scenario is doing?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mikej117 over 8 years ago

Eduardo - thanks, I'll give that a try.
Sally - The Tasks page was reloaded automatically by Appian after the user finished their task.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mikej117 over 8 years ago

Thanks Eduardo, that seems to have done the trick!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 benjamins over 8 years ago

I like to activity chain my nodes all the way to the data store persisting to ensure that the first screen that the user sees is the latest data Mike. Noticed this behaviour a lot when using related actions to update a record and you are using the related actions in the top right of a record view. Once the update was complete, the record wasn't displaying the changes unless I refreshed the view. Chaining saved the day.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel