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?
Good feedback from all.No, this isn't a defect.Appian doesn't poll completed timers for changes. Thus the timer task won't restart based on an update to a referenced constant..
I'm curious about your use case, Erick. Design recommendations these days lean more towards short-lived processes that leverage a relational database for relevant long-lived data.
Have a look at this playbook play to see what I mean.
Hi Erick -
Consider the following, (there's a lot of timer talk in there, hopefully it doesn't make you dizzy):
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.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.