Need a workaround for recurring reservations

[leroysquires]

We are using Workplace Reservation Management to coordinate our return to work process.  Users are able to search for available cubicles, workstations, offices..... for a particular day just fine.  However, when requesting availability for a recurring number of days, the search returns any space that is available on the 1st day of the recurrence regardless of the status of the space on the following days.  There is no indication of a conflict until after submission of the reservation, and even then only if you specifically look for it under the 'Recurrences' tab.

Has anyone built a report or UI that will allow users to avoid selecting spaces with conflicts?

[Arvid]

Hello @leroysquires ,

In the latest version of the Reservation Management application, employees are informed about the space availability within the series.

When creating a recurring reservation, for each available space, a "score" indicates the availability of the space. Handling conflicts can be done automatically or manually, after creating the reservation.

For more information, please see our blog post related to the release: https://www.servicenow.com/community/wsd-blog/workplace-service-delivery-what-s-new-in-the-february-...

Kind regards,

Arvid

[Peter525]

Hi Arvid,

I tried this new feature on a space that has a reservable quantity of 10 and it doesn't look like the score takes reservable quantity into consideration. I am able to make confirmed reservations against the said space before it reaches capacity, but the score shows that the space is unavailable after just one reservation.

Can you confirm if this is intended functionality?

Thanks,

Peter

[Arvid]

Hi @Peter525 ,

I have observed the same and raised an internal defect. As you already mentioned, the space remains available until it "exceeds" its quantity but the indication of the availability is incorrect.

We will address this as quickly as possible in our upcoming releases.

Kind regards,

Arvid

[Peter525]

Thanks Arvid! Looking forward to the fix since this feature is #1 on the wish list for our users.