+11
Hello,
I have requests from customers to be able change status at a given time.
They want to add a date field to the forms and when an agenten sets specific date and time the ticket should set on pending and be reopened on that date and time. If the time node would have had input field where we could use a placeholder from the form and not just hard set.
Seen post about this but couldn’t find them.
+14
Tagging a few people to help get this feature enhanced, we really need the ability to trigger workflow on a specific date and time!!
+14
Hello,
I have requests from customers to be able change status at a given time.
They want to add a date field to the forms and when an agenten sets specific date and time the ticket should set on pending and be reopened on that date and time. If the time node would have had input field where we could use a placeholder from the form and not just hard set.
Seen post about this but couldn’t find them.
Here is a link to where there was some solutions as a way to build this out for the time being.
+11
Hello,
I have requests from customers to be able change status at a given time.
They want to add a date field to the forms and when an agenten sets specific date and time the ticket should set on pending and be reopened on that date and time. If the time node would have had input field where we could use a placeholder from the form and not just hard set.
Seen post about this but couldn’t find them.
Here is a link to where there was some solutions as a way to build this out for the time being.
Ya I saw that but it’s for freshdesk :/ We have a customer that uses PS to make this.
+1
Tagging a few people to help get this feature enhanced, we really need the ability to trigger workflow on a specific date and time!!
My apologies if I had misled you Zachary. In my mind, the timer node was an analogous to a kitchen timer. I spent many years in restaurants before working in technology the timer was always a countdown to another step - pull the potatoes, change sanitation buckets, add the cream, or remove something from the oven, for example. To me, I often look at workflow automator as a recipe and the timer was there to ensure nothing got burnt or was started too early with the idea that everything comes out at the right time.
Can you help me understand your use case for a date node in a workflow automation? This would only work one time, but maybe I am missing something. I can see day of the week, every other Wednesday, etc. but not Dec 10th, 2022. Time does make sense as well - say you want to occur at the start of business hours or 8PM. Is this what you mean by time?
+14
Tagging a few people to help get this feature enhanced, we really need the ability to trigger workflow on a specific date and time!!
My apologies if I had misled you Zachary. In my mind, the timer node was an analogous to a kitchen timer. I spent many years in restaurants before working in technology the timer was always a countdown to another step - pull the potatoes, change sanitation buckets, add the cream, or remove something from the oven, for example. To me, I often look at workflow automator as a recipe and the timer was there to ensure nothing got burnt or was started too early with the idea that everything comes out at the right time.
Can you help me understand your use case for a date node in a workflow automation? This would only work one time, but maybe I am missing something. I can see day of the week, every other Wednesday, etc. but not Dec 10th, 2022. Time does make sense as well - say you want to occur at the start of business hours or 8PM. Is this what you mean by time?
Hey Casey, you didn’t mislead me. I think what would work best is if we could set the timer dynamically via a placeholder. So yes the workflow may only execute once but it would get triggered by the creation of, let’s say, a service request and then allow us to populate the timer delay to delay the workflow until that dynamically placed date and time. Then the workflow would continue. Or...if the field that holds the timer numerical value (“how many” seconds, days, etc) could take placeholders, so that we could use the expression builder to gain a “result” to plug into the field in the delay timer. Hope that helps explain its use. Thanks again!
+11
Tagging a few people to help get this feature enhanced, we really need the ability to trigger workflow on a specific date and time!!
My apologies if I had misled you Zachary. In my mind, the timer node was an analogous to a kitchen timer. I spent many years in restaurants before working in technology the timer was always a countdown to another step - pull the potatoes, change sanitation buckets, add the cream, or remove something from the oven, for example. To me, I often look at workflow automator as a recipe and the timer was there to ensure nothing got burnt or was started too early with the idea that everything comes out at the right time.
Can you help me understand your use case for a date node in a workflow automation? This would only work one time, but maybe I am missing something. I can see day of the week, every other Wednesday, etc. but not Dec 10th, 2022. Time does make sense as well - say you want to occur at the start of business hours or 8PM. Is this what you mean by time?
That you can use a placeholder from a date field in the ticket in the Timenode.
This would set the ticket in pending until that date/time.
Use case would be that you plan to call the customer next week to confirm it worked or the customer are out of office and back that day.
Another use case would be; A manager requests a new user that going to start in 3 weeks. You don’t want to create the user right away due to license costs. You take the placeholder from the request date/time field and paus the WFA that creates the user using a time node. Each item in the kit/bundle has different solution time. Order a computer need to be done direct or x time befor the new user starts to work.
+1
As a workaround, I did the following test in my own instance, but there needs to be additional thought about how to limit when other updates are made to a ticket since these are triggered from a simple condition.
Employee Out of Office using supervisor rule, fields, and automator
Another customer had similar success using the Expression of now( ) (E1 - Expression #1) and then taking that result (E1), and if E1 is greater than “Return from out of office”, condition is “true” kick actions off after.
Using the new hire start date, you could also reference that date/time field for when to start a set of actions.
Does this help as a workaround for now?
+11
As a workaround, I did the following test in my own instance, but there needs to be additional thought about how to limit when other updates are made to a ticket since these are triggered from a simple condition.
Employee Out of Office using supervisor rule, fields, and automator
Another customer had similar success using the Expression of now( ) (E1 - Expression #1) and then taking that result (E1), and if E1 is greater than “Return from out of office”, condition is “true” kick actions off after.
Using the new hire start date, you could also reference that date/time field for when to start a set of actions.
Does this help as a workaround for now?
Hello
Hmm, I tried to create the supervisor rule but couldn’t find the date field in the dropdown list.
Other than that, it looks promising.
I guess you could use due date, set the due date using a WFA and API and then supervisor to reopen the ticket when due date is 0. Not tested it. But Chaning the due date could mess up the SLA if you are picky about that.
+14
Wow
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
