My Oracle Support Banner

Setting The Number Of Repetitions In A Non Interrupting Timer Start Event Does Not Work (Doc ID 1587116.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle Business Process Management Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal

An event sub-process is designed to be triggered using a non interrupting timer start event and its repetition is set to 1.

In this case, the event sub-process is triggered whenever the timer condition is met keeping repeating and the number of repetitions is not taken in consideration. The timer start event should be triggered only once because the repetition is set to 1.

Documentation indicates that "Repetitions: enables you to define the number of times the event runs. After the event runs the number of times you defined, it stops running."

 

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
 Steps to reproduce:
 1. Create new BPM-Project with one Asynchronous-Process  
2. Create Timer-Start-Event and add just one more End-Node. Nothing needs to
be done in the process
3. Set the Timer-Event to interval of 5 seconds with Repetitions = 1
4. deploy project and monitor in enterprise-manager-console that every 5
seconds a new Process Instance has been created.

Expected behaviour would be only 1 Process Instance....
Solution
 <<In the documentation for PS6 at  http://docs.oracle.com/cd/E28280_01/doc.1111/e15176/timers_bpmpd.htm#CIHEECCI,. 
  In section 17.7.5, documentation for repetition is provided for timers. Repetitions are not implemented yet for start timers. The document needs to  be corrected. >>
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.