Automation Variables
K
Keaton Garner
Hey, we're having a problem with a variable in the automations. The variable is
/Project.Service Ticket start date
. This variable comes in the format of YYYY/MM/DD HH:MM:SS. This should be good for a service where you have the exact date and time scheduled. But we also want to use this variable for scheduling windows a week ahead. The issue we're running into is when we leave the time blank on a date, it automatically inputs 19:00:00 for the time.These variables should probably be separated, to make it more versatile. You should have
{startDate, dueDate, startDateTime, dueDateTime}
all as different variables so you're not restricted to how you have to format the email/text.Here are two examples we'd like to use:
- The estimated service date is between startDateanddueDate.
- The Technician should be arriving between startDateTimeanddueDateTimeonstartDate.
Nick Torres
measuring this is critical to efficiently grow teams optimizing for productivity by these metrics, excited to see this happen