The timer will adjust to the units that makes the most sense for the time period. I have a timer component that is set as a "Count up timer" using the time since a case was created. If the time period is short it displays hours and minutes.
If the time period is long it automatically switches to months & days:
The timer will adjust to the units that makes the most sense for the time period. I have a timer component that is set as a "Count up timer" using the time since a case was created. If the time period is short it displays hours and minutes.
If the time period is long it automatically switches to months & days:
does it require more resources to have several business processes left "executing" (waiting for a timer condition to be satisfied to do something) or to have a single process scheduled to run every 5 min (i.e) that searches for some record that has a "due date" condition close to the current date time?
the difference would be that the former would be left "pending" for sometime, and the latter would terminate.
The better approach in this case - is to have a single scheduled process that will be executed fastly.
Because each process, that is executing in background mode using 1 thread of quartz worker (Default value = 5 workers). So, if you will start a lot of the background processes, that are executing (waiting for some event) - you can overfill the background processes queue and new background processes will not start correctly until the old processes are not finished and the quartz worker is not free for a new task.
The better approach in this case - is to have a single scheduled process that will be executed fastly.
Because each process, that is executing in background mode using 1 thread of quartz worker (Default value = 5 workers). So, if you will start a lot of the background processes, that are executing (waiting for some event) - you can overfill the background processes queue and new background processes will not start correctly until the old processes are not finished and the quartz worker is not free for a new task.
I want to use Wait Timer element in multiple business processes. I want it to wait upto 28 days. Will there be any issue if I specify 28 days (24,19,200 seconds) ? or is there any recommendation what is the maximum wait duration can be given?
Please be informed that the [WAIT FOR TIMER] element will not work correctly with such a big value, it will definitely drift off the needed amount of time at some point. Could you please elaborate on what business logic you're trying to implement, so we could try to find a possible alternative for you?
I'm sorry for the confusion, we have double-checked this functionality with our R&D team and they confirmed, that Wait Timer will work correctly even with such a big value specified. Please feel free to try it out and in case you do face any issues, make sure to register a case for our support team.
