Overdue Process alert (7.6 on-demand)? 

Hello Eric,

You'll want to use a divergent parallel gateway for this. Check out the example I've linked to in our documentation. The screenshot and explanation are doing precisely what you need.

Hope this helps!

Jill

Hi Jill,

Thanks for your prompt reply.

For some reason I it doesn't move past the timer.

I set the timer for one minute and nothing happens.

I set it through fixed time with criteria: "date created + 1 minute" and still doesn't budge.

I will have to open a ticket.

What is the criteria for the "count +1" action?

I will keep working during the weekend and revert.

One more question:

How do you suggest i do with the other options? (as my first image)

as I have International, US, AU, China, and NZ rules.

Thanks

H

Correction - I see you used the parallel gateway. You'll want 2 of them though, one for each possible outcome. In this example, the reminder message will send at regular intervals until the activity is completed and the process terminates, or until the loop times out due to the error number of cycles setting in your admin panel.

I've attached the .bpm file but you will need to configure the settings for each element and then enable the Process Definition for testing. Hopefully it gets you a head start!

Let me know if I missed anything.

Jill

Eric,

Continuing on what Jill mentions, in order to get events to move beyond the timer when the time threshold is met, you will need to ensure that the Process Author Scheduled Job is triggered in Admin > Schedulers.  Once this scheduler job is triggered, and the time threshold is met in a process, the process should then move to the next event in the process.

Hope this helps,

Lori

Eric,

Continuing on what Jill mentions, in order to get events to move beyond the timer when the time threshold is met, you will need to ensure that the Process Author Scheduled Job is triggered in Admin > Schedulers.  Once this scheduler job is triggered, and the time threshold is met in a process, the process should then move to the next event in the process.

Hope this helps,

Lori

Hi Lori,

Thanks for your input.

Double-checking, I noticed that this situation only occurs in the sand-box.

I checked the cron jobs and they look fine. I will probably have to open a ticket.

The timer is working fine in the live environment.

Thanks again for your help.

Cheers,

H