Hi All, I have configured a process model Start Event with Timer recu

mohamedt808 over 9 years ago

Hi All,

I have configured a process model Start Event with Timer recurrence.Am using expression to define interval in which it has to repeat. i.e. 9 am to 12 am repeat 60 minutes once and 30 minutes once till 6 pm (I have chosen at an interval options).Also i am using some expressions in timer conditions which will return true for specified timeline and false for the other case.

But What i have found is once published the process model it keeps on running on the time gap it has found on the first execution .say i have published it on 10 am then first time it gets 60 minutes as interval and it keeps on running on 60 minutes interval even after 12 am.Also on the timeline where the timer condition will return false.

Below is the expression i am using find the time interval
if(and(hour(local(now()))>(8),hour(local(now()))<12),60,30)
and in timer condition am using below expression
if(or(and(hour(local(now()))>(9),hour(local(now()))<12),and(hour(...

Discussion posts and replies are publicly visible

Parents

0 Chris over 9 years ago

You may be running into the same issue as when setting the start event time based on a constant - after the model is published, the initial constant value is always used even if the constant is updated.

What I would do is simplify the start event timer - set it to every 30 minutes. Have a decision node at the start of your process decide whether to continue, or to end without processing. If between 9 am/12am (did you mean 12 pm?), allow to continue every other iteration - using a constant as a flag maybe, update constant accordingly based on the last run or no run. If otherwise and before 6 pm, allow to continue on each 30 minute interval, otherwise, simply end the process if not in the designated timeframes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 9 years ago

You may be running into the same issue as when setting the start event time based on a constant - after the model is published, the initial constant value is always used even if the constant is updated.

What I would do is simplify the start event timer - set it to every 30 minutes. Have a decision node at the start of your process decide whether to continue, or to end without processing. If between 9 am/12am (did you mean 12 pm?), allow to continue every other iteration - using a constant as a flag maybe, update constant accordingly based on the last run or no run. If otherwise and before 6 pm, allow to continue on each 30 minute interval, otherwise, simply end the process if not in the designated timeframes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data