In almost every implementation, custom actions to a booking become necessary. Having to open the booking and calling logic by clicking a button or running an ondemand workflow is quite cumbersome for a dispatcher. Suggestion: To achieve maximum flexibility, provide the ability to register custom workflow actions per entity type.

Under Review
Ideas Administrator

Thank you for your feedback!

This is a great suggestion! We will consider this in our roadmap.



Vinay Nalam,




The logic for custom actions should also extend to allow for "duplicating bookings" [Similar to selecting a booking on the schedule board, selecting the work order number, then selecting 'book' from the commands].

Category: Universal Resource Scheduling


We really need to be able to add and remove menuitems. In our case we have downstream logic where we need to Delete a booking in an integrated system. That can not be accessed with the current Remove-menuitem. So we need to add our own "delete" and remove the Remove to avoid confusion for end-users.

Category: Universal Resource Scheduling