|
You can model loops in process diagrams to replace the
retry feature of the following actions in upgraded processes:
-
EmailReceiver (replaced with Receive operations of the
Email service)
-
QueueReceiver (replaced with Receive Message From Queue operations
of the JMS service)
Both the Receive Message From Queue operations
and the Receive operation automatically catch the MessageNotFoundException
event type. You can use the event catch to implement a loop that
causes the operation to execute repeatedly until a message is found.
The loop can include a scheduleWait operation (Wait Point service)
that controls the frequency of retries.
A route begins at
the event catch and ends at the scheduleWait operation. Another
route begins at the scheduleWait operation and ends at the Receive Message
From Queue operation or the Receive operation, depending on your process.
If
the Wait Point service is not available, you can use a timer event
type instead. In the loop described above, instead of a scheduleWait
operation, a timer event is thrown and received in sequence.
If
you want to retry for a specific number of times, you can add a
counter to the loop. (See
Loops
.)
|
|
|
