Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Order and Service Management (Communications Industry) (MOSC)

OSM 7.3.x Enhanced Order Processing and Fallout Management - Task Execution Modes

Dec 22, 2015 11:15PM edited Dec 23, 2015 3:11AM in Order and Service Management (Communications Industry) (MOSC)

Traditional Approach (Prior to OSM 7.3.x versions) of Handling Task Failures in OSM

Implement specific fallout task
- Implemented for each task that can fail
- E.g. For any Task A, a fallout for Task A is implemented
Loop task transitions back to the originally failed task
- E.g. The fallout for Task A loops back to retry Task A
Drawbacks
- Additional process modeling
- Incorrect flow during compensation

New Approach (From OSM 7.3.x versions) - New Task Execution Modes

Categories of Task Execution Modes
- Normal Mode for normal task processing
  - Supported Execution Modes are Do, Redo, Undo and Amend-Do
- Failed Mode for troubleshooting fallout tasks

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month