The mobile app's Latest events feed brings together changes saved to records. You can use it to see who created or updated a task, service request or message, and open the actual record to check its details. The events feed is neither a list of current work nor a complete change history for the organisation.
Open and refresh the events feed
Select Home in the navigation at the bottom of the app. The events feed is on this tab; Browse opens the folder and Spot browser.
- Android: tap the heading row of the Latest events feed section.
- iOS: tap the arrow button to the right of the Latest events feed heading.
Opening the section fetches events from the server, so you need a working network connection. Events are shown by event time, from newest to oldest. Scroll to the end of the list to fetch more rows if any are available.
To fetch the latest events again, close the section using the same heading row or arrow button, then open it again. Fetching starts from the first page. Closing the section does not delete the saved history.
Understand an event row
Check who made the change, the item type, the item name or message content, the event description, and the date and time. Both apps show event times in Helsinki time, even when the device uses a different time zone.
The description usually indicates that a record was created or updated. When the status of a task or service request changes, the row may show the status after the change. The row is a summary: it does not list every changed field and its old and new values.
The item name is taken from its current details. If a task is renamed, the new name may also appear alongside an old event. The text of a message event comes from the message's current content. You should therefore not interpret the name or content shown in the row as information from the time of the event. The status shown for an old event may not be the work's current status either.
Open the actual record
On Android, tap the item name highlighted in blue in the event description. On iOS, tap the event row. Task and service request events open the details of the corresponding work item. If the list shows an event related to a Spot, the same action opens that Spot's details.
A message event opens the message list, where you need to find the message you want. It does not open that message's details directly.
Before processing the work, check the record that opens to confirm that you have the correct item and its current status. Reading the events feed does not start a task or mark a task or service request as done. Always use the record's own actions to process it, and check the result in its details.
However, views opened in connection with the work may have their own read markers. For example, a task's comments view may mark the work chat as read when the task is not read-only for the user. This is a separate read marker, not confirmation that the work is complete.
What does the events feed contain?
For a regular mobile user, the server selects up to 100 most recently updated tasks, 100 service requests and 100 messages separately from the records the user has permission to access. History rows related to these records are fetched for the events feed, subject to the other filters.
The limit applies to records, not the number of events. Several changes may appear for the same task, so there may be more than 300 rows. There is no fixed time period: the history of a selected record may include old events. Conversely, events may be missing for a record that is no longer among the 100 most recently updated records.
The server excludes, for example, time entries, changes to users and user roles, and separate history rows for service request additional fields. Some updates that only change time or user information are also excluded: for example, updating only the processing start time and the user who started it, without any other change, does not appear in the feed.
In addition, the mobile apps may omit an event if the name of the person who made the change, the item type, the event information or the item name is missing. A missing event row therefore does not prove that no change was made.
If an expected event does not appear
First, check that you are viewing the correct organisation's records and can open the actual task, service request or message. Fetch the events feed again by closing and reopening the section. If necessary, scroll to the end of the list to load more rows. Bear in mind the limit on the most recently updated records and the changes that are excluded.
To check the current work situation, use the actual task or service request list. If needed, see the instructions for finding your own tasks and checking work details.
For a closer look at individual changes, there is a separate Change history in the browser. Problems with transfers between systems are investigated using the integration event log. The mobile events feed does not replace either of these.