| Booking confirmed triggers are firing repeatedly for the same guests | Booking confirmed triggers were firing repeatedly for some guests. |
| Add | RENTAL:DIRECTIONS |
| The translation section disappears when you add a translation | When adding a translation, the translation section would disappear from the template editor, until a page refresh |
| Trigger conditions for triggers created via sample showing Invalid Date for the creation timestamp | The timestamp on the trigger conditions (for triggers created using samples) was showing as Invalid Date |
| Last-minute checkin trigger sample has undefined time values in the trigger condition | The days/hours fields in the trigger condition on the last minute trigger (made using samples) was showing the value Undefined |
| Some trigger event types appear in the workflow details, but not in the booking details | Specifically, invoice triggers were not appearing on the booking details overlay, even though they were visible in the workflow details overlay |
| Directions data dictionary code is parsing as blank | Driving directions data code was showing as blank in the sent template |
| The subject field disappears when updating a template | The subject field was disappearing when saving a template, and choosing the option to update instead of save as new |
| "Creator" Value doesn't display when you create a custom code | The creator of the custom code was not showing when a new custom code was created |
| Issue: Booking status is paid trigger condition was not allowing some triggers to fire | The paid status of the booking was not being recognized properly in some instances, but now it works correctly under all conditions. |
| Cross icon doesn't display to close overlays (iPad) | The close overlay button (X) was not displaying properly on ipads |
| When duplicating a trigger with a specified trigger condition, the condition points to the trigger from the original workflow | Duplicating a trigger that has a specified trigger condition was pointing to the specified trigger of the original workflow, instead of the specified trigger of the new workflow that the trigger was duplicated to |
| Duplicating workflows causes issues with the specified trigger condition | Duplicating workflows was resulting in all the triggers from both the original and new workflows appearing in the list of triggers when editing the specified trigger condition. This created confusion, as users weren't sure which trigger to select since the trigger names get duplicated in the process of duplicating a workflow. |
