Timer event - Delay until the DATE AND TIME specified

Question

I have a process that gets kicked off given a date and TIME specified by a DATE AND TIME constant. So in my start event, I have a timer and I selected the option to Delay until the Date and time specified by the expression where I have a constant. 
 Say I want the process to kick off tomorrow at 7:00 AM then I would make the constant 7/24/2018 7:00 AM. That is working perfectly fine. However, if I want now the process to kick off a second time at 1:00 PM on the same day, the process is not getting kicked off. 
 I am thinking the timer is not looking at the TIME and it is looking at the date only. Is this an Appian defect?

Robert Shankin · Accepted Answer

Hi Erick - 
 Consider the following, (there's a lot of timer talk in there, hopefully it doesn't make you dizzy): 
 
 When instance #1 of the re-cert process runs, kick of an asynchronous re-cert timing verification process immediately. The start task of this verification process flows directly into a timer that waits 5.5 months after the timer is a task form that's assigned to the re-cert Admins. 
 The task form in the timing verification process doesn't update a constant, instead, it flows into a new asynchronous instance of the re-cert process that also has a timer following the start task. 
 
 Configure an exception timer on the admin task, in case it gets ignored, and just start the re-cert process at 6 months. 
 If an admin changes the date on the task form, before the exception timer hits, that's the date that goes into the timer in the re-cert process.

Have a look at this sketch (below) - I'm illustrating two processes on the same palette (in different swim lanes) in an effort to keep it simple. You'd need to build out 2 process models in true practice.

hedn89 · Answer

Hi Erickp, 
 
You need to configure two timer events in the start event. One for 7:00 AM and second one for 1:00 PM. Appian will kick off the process at both the times specified. Please let me know if this works. 
 
Thanks

Brazil Vibanco · Answer

Hi erickp, 
 
AFAIK, as everybody mentioned, you have to set two different triggers. 
On your case, the process model is getting its start time value from the constant, getting the constant value at the moment the process model is published. So, if you update the constant later, the process model will still be having the same value as when it was published, it won't take the new value unless you publish again the PM.