Use case: We are using Process Automation to automatically deploy permanent bookings. When the booking starts I want to run an automation that feeds in the ServiceID of the booking (or the ReservationID which I can use to get the ServiceID). Tried using the “Created Booking Action” property on one of the nodes in the service definition, but this runs too early, as the booking\service isn’t fully formed yet. Is there another property I can use somewhere that will only run once the booking actually starts?
Hi Cyrus,
‘Create Booking Action’ script is used at booking time. In case you want to execute a custom script when the booking starts, this should be done from within the LSO script.
I think it should be possible by adding an action to START in the service definition:
If you already have a script attached to the start action, maybe you can call the script you want to run from the already running script?
Hi Cyrus,
The custom script can also be triggered on the pre-roll or start actions of the booking.
On the service definition, we can specify actions. These actions can correspond to the pre-roll, start, stop and post-roll events.
The action script is called an LSO script or life-cycle service orchestration script referring to the start/stop/pre-roll/post-roll actions. The SRM package comes with a LSO script template that can serve as an entry point to run your custom actions. You can find the template under Automation > ‘SRM_LSOTemplate’.
Kind regards,
Robin
this is great thank you!