Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle BPM Suite 12c Modeling Patterns

You're reading from   Oracle BPM Suite 12c Modeling Patterns Design and implement highly accurate Business Process Management solutions with Oracle BPM Patterns

Arrow left icon
Product type Paperback
Published in Sep 2014
Publisher Packt
ISBN-13 9781849689021
Length 454 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Vivek Acharya Vivek Acharya
Author Profile Icon Vivek Acharya
Vivek Acharya
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Flow Control Patterns 2. Multi-instance and State-based Patterns FREE CHAPTER 3. Invocation Patterns 4. Human Task Patterns 5. Interaction Patterns 6. Correlation Patterns 7. Exception Handling Patterns 8. Adaptive Case Management 9. Advanced Patterns A. Installing Oracle BPM Suite 12c Index

Force-Error Execution Exception Handling Pattern


The following table highlights some important facts about the Force-Error Execution Exception Handling Pattern:

Signature

Force Error Execution Exception Handling Pattern

Classification

Exception Pattern

Intent

The intention is to handle the exception raised by the invoked (called) process/service in the invoking (calling) process/service.

Motivation

Handle exception in the invoking activity using a boundary event.

Applicability

This pattern is used to showcase those scenarios of exception handling where the exception is not handled by the invoked process/service by itself. That exception will propagate outside the invoked process/service and is caught by the attached Boundary Catch Event. From there, the process token is allocated to a subprocess which lands into error.

Implementation

If you check the process state diagram and look into the INVOKED state, the sequence "J" points to the scenario where the invoked process...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image