Automata Updates | January - October 2020
-
New Features
Updated: The send to guest option was removed from rate events. This is because there is no reason to send a guest a rates notification.
Updated: The data token |GUEST:WIFE| has been updated in the data dictionary to |GUEST:SPOUSE|. users with templates that still say |GUEST:WIFE| will be unaffected. Both WIFE and SPOUSE data tokens will parse the same thing into the outgoing message.
Updated: Users can now filter triggers on the Triggers page by action performed.
Updated: Saving a custom code with a name that has only numbers was creating issues for some users. We will no longer allow names that are only numbers.
Updated: We added the user role underneath their name in the upper-right corner of the dashboard.
Updated: Users will now be able to set conditions on a trigger before saving. As long as all required fields in the trigger details have been completed, the trigger conditions will become available to be added. This will allow users to create triggers for multiple rentals at once, and have all of them share the same trigger conditions.
Updated: The trigger condition section now appears once all of the required fields are completed in the trigger details. The user no longer has to click the Save button to see this section appear. This should be more intuitive.
Updated: When archiving an active trigger, a pop-up now appears asking the user if they want to disable the trigger before archiving. This will prevent the confusion of archived triggers firing for some users.
Updated: A new Automata Portal has been added to the Help widget. This allows users to submit and vote on suggestions for new features in the app.
Updated: The Exclusion List switch, on the trigger overlay, has been given a label, to go along with the tooltip that was already in place. This should make it easier to understand what the switch does.
Updated: Sympl and Checklist logos were added to the login page. This allows users to quickly navigate to those new products directly from the Automata login page.
Bug Fixes
Fixed: New templates were automatically replacing existing templates on triggers.
Fixed: When duplicating workflows, the triggers in the new workflow were not copying the channel filter selection.
Fixed: When selecting the action Send Signature Form, the template selector was just 10 forms, instead of all forms if the user had more than 10. This has been corrected.
Fixed: Tokeet Widget triggers were not firing for inquires created via widget. A change has been made to the inquiry widget HTML code, that will not allow Automata to capture these events. You will need to make the inquiry widget again in TV3, in order to copy the updated HTML code to your website.
Fixed: Trigger conditions were not visible for triggers that had a hyphen in the trigger name. This issue has been corrected, and the pre-made samples have had any hyphens removed, in order to prevent future conflicts.
Fixed: Webhook service experienced a brief interruption in operation. This issue was quickly resolved, and webhook triggers should operate properly now.
Fixed: On the Booking page, the Last Triggered column was no longer showing the last trigger that fired. This issue did not prevent triggers from firing, and has now been resolved.
Fixed: Triggers were no longer firing for task events. The issue has been resolved, and task triggers now fire as expected.
Fixed: When an inquiry-related data token was included in a Signature contract, sending the contract using an Automata trigger would sometimes result in only the Tokeet User receiving the contract, and not the guest. After the fix, the Tokeet User and the guest receive the triggered contract in all situations.
Fixed: When a trigger was unsuccessful, and a error message was available for the situation, the error log was no longer visible in the dashboard. After the fix, the error log is now available for unsuccessful trigger that have qualified error messages. This can be viewed on the Recent Activity page, with the Error Log action, or on the trigger activity tab, by clicking on an event entry in the table.
Fixed: On the Booking Details overlay, the Messages tab was no longer showing the messages that had been send for the booking. After the fix, messages that were not visible before, will now be shown.
Fixed: Users with a valid Tokeet trial were being shown the banner saying that Automata would not work without a valid subscription, eventhough the app was still fully functional. This banner now only shows when there is no Automata subscription, and a Tokeet account is no longer on trial.
Fixed: The Insert Link button for inserting hyperlinks into a template was not working for some users. This has been fixed.
Fixed: The |RENTAL:WEBSITES| data token was not properly inserting the Tokeet website URL into outgoing templates. This has been fixed.
Fixed: When editing templates in multiple triggers, the first template that was edited was being assigned to the other triggers that were edited afterwards. This has been fixed now.
Fixed: Message templates were assigned to the wrong triggers. This occurred when editing multiple templates in multiple triggers. This issue has been fixed.
Fixed: The delete button on the Templates page was enabled, even when no templates were selected in the list. This issue has been fixed.
Fixed: When editing the column headers on the Triggers and Bookings pages, the column options were displaying in multiple rows. This issue has been fixed.
Fixed: When inserting a hyperlink into a template, the URL field was not visible through the sides of the template body window. This issue has been fixed.
Fixed: When a contract trigger fired, the guest name and channel name were not properly displayed on the Recent Activity page. This issue has been fixed.
Fixed: Some users received a bad request error message was appearing when attempting to save a template or trigger. The template and trigger would still save correctly, but the error message created some confusion. This issue has been fixed.
Fixed: When creating a workflow from a sample, the different sample options were not displaying the correct collection of triggers. This issue has been fixed.
