USAGE OF INTERMEDIATE EVENTS
INTERMEDIATE EVENTS MESSAGE INTERMEDIATE EVENT :receiving message events receive a message during process execution. Message intetmediate events appear in the process flow and cannot be attached to activities. The message intermediate event has two flavours
1)start alone listener:It is seen with in a bpd as its own.
2)attached listener:It is attached to an activity
There is an check box to select
An option available on an attached listener determines whether or not the outgoing link from the activity will also be followed when the activity completed.
DURABLE SUBSCRIPTION:If they flag is checked then arrival of an event before the listener is reached is remembered and when the process reaches the intermediate message event. it is immediately notified that the solution can continue.
If not checked discarded and the process will wait for a further event.
Uca we will give
(i) uca name
(ii)define how it is started
on event:when message comes
time elapsed:particular time period field on schedule from the run time.
(iii)what data mapping service is associated service with it.
The enabled checkbox is used to enable or disable the execution of the associated service when an event arrives.
TIMER EVENT:A timer has an associated “trigger on "attribute .this is an algorithm used to select when the file is file .The choices available are
1)after start of step
2)before due date
3)after due date
4)before custom date
5)after custom date