Auto Actions: Difference between revisions
Jump to navigation
Jump to search
| Line 250: | Line 250: | ||
<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> This filter will not apply if you are triggering on a single property. | <span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> This filter will not apply if you are triggering on a single property. | ||
== Using Smart Logic Template Variables == | |||
You can use smart logic template variables to trigger auto actions for specific conditions. | |||
If you want to send a message on a specific day of the week :- | |||
1) You need to send a message to remind the guests to put the rubbish bin out for collection on a Wednesday night. | |||
* [IF=:[CURRENTDATE:{%u}]:3:yes|no] will test if the current date is a Wednesday | |||
2) Remind the guest that the cleaning lady will be at the apartment on Friday morning. | |||
* [IF=:[CURRENTDATE:{%u}]:4:yes|no] will test if the current date is a Thursday | |||
%u ISO-8601 numeric representation of the day of the week 1 (for Monday) through 7 (for Sunday) | |||
== Performance and Testing == | == Performance and Testing == | ||
Auto actions will test up to 1000 bookings per cycle, if your trigger condition involves more than 1000 bookings, the next 1000 will be tested on the next cycle etc. | Auto actions will test up to 1000 bookings per cycle, if your trigger condition involves more than 1000 bookings, the next 1000 will be tested on the next cycle etc. | ||
If you require the fastest speed | If you require the fastest speed, ensure your trigger is designed to test less than 1000 bookings. | ||
The easiest way to do this is usually by reducing the testing window to the smallest necessary and adjusting the trigger condition to the most suitable. | The easiest way to do this is usually by reducing the testing window to the smallest necessary and adjusting the trigger condition to the most suitable. | ||
For example a trigger that tests all bookings from booking time for 1 year will test many bookings while a trigger that tests only the 7 days before check-in will test less bookings and perform faster. | For example a trigger that tests all bookings from booking time for 1 year will test many bookings while a trigger that tests only the 7 days before check-in will test less bookings and perform faster. | ||
The test tab of the auto action has a button | The test tab of the auto action has a button that will show you how many and which bookings are being tested by the auto action. | ||
It is also possible to specify a booking number and test if the auto action would trigger on that booking with some diagnostics information shown to help trouble shooting. | It is also possible to specify a booking number and test if the auto action would trigger on that booking with some diagnostics information shown to help trouble shooting. | ||