I'm using the ScheduAll protocol to trigger an automation script, but when a booking is copied in ScheduAll it doesn't trigger the automation script, even though the valid state for new work orders is set to any, and the state transition is set to any any.
It only triggers the automation script if the state is changed in ScheduAll.
We're currently running 22.214.171.124 version of the protocol.
In order to trigger an automation script from Work Orders modification, either they're new or because some of the fields were changed in the Work Order itself or in the fields of the resources associated to it, I'd recommend the usage of the 2.0.3.X where you have an enhanced version of the script triggering which allows an advanced configuration.
Please find below an example where the automation script defined in the 'Task Automation Script Name' parameter will be triggered upon change of the Work Order Status for the status defined in the 'Previous Status' and 'Current Status' columns as well as for new Work Orders that appear on the table in the 'Confirmed' or 'ConfirmedByDataMiner' status.
For more details, please check the tool-tip of the parameters defined in the referred page by hovering the mouse over the parameters.