Blog

Automation Rules Can Consult Calendars

November 23, 2022

Patrick Bakker

1 Min Read

Click To Explore

Automation rules can now access calendars in Xurrent, such as work hours or support hours calendars, or any other calendar. That calendar can subsequently be used to calculate a target time using a start time and a duration. The target can be calculated with the new target_at operator, and the duration between two times using the duration operator.

To demonstrate how this may be useful, we can take an example from Widget Europe, Information Technology. For the workflow template ‘Registration of a new Widget product in SAP’ an automation rule exists to notify an approver when the approval task takes too long, in this case 1 day.

This automation rule does not consider normal working hours. So if the task is assigned to an approver on Friday afternoon, the approver will get a notification on Saturday afternoon, when the approver is not working. This can now be resolved by using the new target_at operator. By retrieving a calendar (which can also include holidays), the automation rule can now be updated to take working hours into account.

Partners

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.

3 Mins

July 1, 2026

Service Management

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.

8 Mins

May 30, 2026