Currently under AutomateWoo > Tools there’s the “Reset Workflow Records” option but that option “Deletes all logs, queued events and conversions for a workflow.” There should be an option as well to delete a workflow’s log data without automatically deleting queued events. I understand why conversions would be deleted when logs are being deleted as […]
We frequently have flows where logs are completely irrelevant but we can’t enable the site-wide option to not keep logs at all, or reduce the timeframe logs are kept for all flows because some flows do rely on filters like ‘last workflow run’ or ‘workflow run count’. This means we constantly have to clean logs […]
I understand that as of AW v6.5.0 a fix has been released for “Customer Email rule quick filter not finding orders placed by registered customers whose billing email differs from their account email.” so I’m assuming that the AW rule filter “Customer – Email” now assesses both the account/login email and the billing email but […]
We have the below options to filter workflow triggers for customer-scoped rules: Customer – Country Customer – State Customer – State – Text Match Customer – Shipping State Customer – Shipping State – Text Match Customer – Postcode Customer – City Customer – Phone Customer – Company Yet, for order-scoped rule filters we only have […]
It would be great if the rule filter operators could be extended so that the Is / Is Not Blank (i.e., “is set” and “is not set”) are available for ALL relevant rule filters. Currently, certain filters like “Customer – State” or “Customer – Shipping State” (or similar customer/order/subscription-scoped rule filters) only have the options […]
Allow deletion/auto-cleaning of historic workflow logs while still keeping rules/filters based on “workflow count” intact without moving stored log data to order meta (which would only shift the storage overhead elsewhere rather than fully addressing/optimising the database). Currently, when any of the logs are deleted, workflows that rely on those logs for the “workflow count” […]
We’d love to be able to trigger emails depending on whether a customer decided to renew their subscription early to send them extra info about how their existing/new billing cycle works. Either introduce a new ‘Subscription Renewed Early’ trigger, or a filter that could be used when ‘Subscription Order Created/Paid/Etc.’ is triggered.
The ability to add if/else statements in the email content to define what appears. Should work with custom variables. Use case example -> a bookable activity which could be multiple days or only one day: {% if order.start_date == order.end_date %} Date: {{ order.start_date }} {% else %} Start date: {{ order.start_date }} End date: […]
It would be great to have an option to send Booking reminders out at a defined time before a particular course date.