Triggers that compare multiple date fields from a ticket.
I would love a trigger that can compare two custom date fields in a ticket and take an action based on that. The way that triggers on date fields currently work only let you compare a date field to a static date, which seems to have a limited set of uses.
My use-case is that I am working on a ticket form for customers to submit a claim for a warranty if their product that they bought from us has failed. However, our warranty lasts 2 years from the date that the purchase was made. The ticket has to enter the date of purchase and date of failure as custom date fields on the ticket. It would be great if there was a trigger that checks that the date of failure was within 2 years of the date of purchase, and could either send a notification email that the warranty period has expired, or could update the status of the ticket, etc..
Also I could add a check that makes sure that the date of purchase happened before the date of failure, just to confirm the data in the tickets makes sense.
I'm aware that you can compare a date field to the day that the ticket was created, but in we'd like to avoid this as claims being submitted rarely occurs the same day that the failure occurs.
-
Official comment
Hi Austin Shaw - thanks for submitting your use case. I've captured this in our product feedback tool for future prioritization. While comparing date fields via triggers isn't currently on our roadmap it always helps to hear your feedback so we know we are working on the right things to solve your biggest workflow problems!
Currently we are working towards extending the data that can be used in triggers to non-ticket data. This comes as part of the Custom Objects EAP.
-
Thanks for the feedback, Austin!
-
Would love this too! And the ability to set an internal date field based on a date input by an end user.
-
We would also love this! We're looking at a workflow where a process goes forward of two dates match, and right now we're having to do some Zapier juggling. Would much rather do this natively!
Ideally, the ability to match any two fields would be amazing. -
Also a need here.
Please sign in to leave a comment.
5 Comments