Seeing the different states in the SRM Framework and in the Bookings module in Cube might be confusing.
There's a distinction between the booking stages in the core software and the booking life cycle when the SRM framework has been deployed, but is there a complete list of the booking states in the core software?
SRM Framework
Cube Bookings Module
Hi Jan-Klaas,
I have created a list of the different core software states below. As this information is missing from the 'booking stages' documentation page you linked, we will update that page to include such an overview.
- Pending: Bookings with this state will reserve the assigned resources, but will not execute any scripts or actions.
- Confirmed: Bookings with this state will reserve their resources and orchestration will be executed at the configured times.
- Ongoing: The Resource Manager will move bookings from the 'Confirmed' state to the 'Ongoing' state after running the start actions. It is not possible to assign this state to a booking yourself, the Resource Manager will always convert it to the 'Confirmed' state when trying to do so. More info about the start actions can be found in the documentation page.
- Ended: The Resource Manager will move bookings from the 'Ongoing' state to the 'Ended' state after running the end actions. Like with the 'Ongoing' state, it is not possible to assign it to a booking yourself. More info about the end actions can be found in the documentation page.
- Interrupted: If a booking misses their start, stop or any orchestration event because the hosting agent was down, the Resource Manager will move the booking to this state. The documentation page also contains some information about this.
- Canceled: The resources assigned to the booking are free to be used by other bookings, and orchestration will not be executed. The Resource Manager will never automatically assign this state, the booking must be updated from a script or similar to go to the canceled state.
Hope this helps.