Insights & updates from our experts
Finished Tasks Separated in Self Service Inbox
At the bottom of the ‘My Inbox’ section, the Xurrent App and Xurrent Self Service used to list the change tasks and the project tasks that were assigned to the user and are already finished. The reason for listing the tasks that are already finished was that end users need to be able to look up the tasks that they were involved in. This allows them to, for example, check the summary PDF of a project that they approved.
But it is a little strange to see those finished tasks so prominently in the inbox, when the user is not expected to work on them anymore. That is why the finished tasks now have their own separate view in the ‘My Inbox’ section. People can open this view when they are in the ‘My Inbox’ section by pressing the 3 little dots (i.e. the vertical ellipsis) and selecting the option ‘Finished Tasks’.

This opens the ‘Finished Tasks’ view, in which they can see all the change and project tasks that have reached their final status and where the person who opened this view is (one of) the assignees.

The final status of a task can be one of the following status options:
- Failed
- Rejected
- Completed
- Approved
- Canceled

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














