Business events trigger Orchestration flow then why there are business events in action type

 Excellent question πŸ‘ — this is exactly where most confusion happens in

Dynamics 365 Intelligent Order Management

You’re right:

Business Events trigger orchestration

So why are they also present in Action Type?


🧠 The Key Idea (Most Important)

πŸ‘‰ There are TWO types of business events in IOM:

TypePurpose
Trigger EventsStart orchestration
Outcome EventsContinue orchestration

πŸ”· 1. Business Events (Trigger level)

These are:

πŸ‘‰ External or initial events

Examples:

  • Order Created

  • Order Updated

✔ These START orchestration


πŸ”· 2. Business Events in Action Type (Outcome level)

These are:

πŸ‘‰ Internal events generated AFTER an action runs

Examples:

  • Fulfillment Completed

  • Fulfillment Failed

✔ These CONTINUE orchestration


πŸ”— Full Flow (This is the missing link)

[Business Event - Trigger]
Order Created

Orchestration Rule fires

Action Type selected

Provider Action executes

[Business Event - Outcome]
Fulfillment Completed / Failed

Next orchestration step

πŸ’‘ Why Action Type needs Business Events

Because IOM needs to know:

πŸ‘‰ “After this action runs, what event should I raise?”

That’s exactly what these fields define:

  • Business Event Success → next step trigger

  • Business Event Failure → error path trigger


🎯 Real Example

Step 1 (Trigger event)

  • Order Created


Step 2 (Action runs)

  • Send order to warehouse


Step 3 (Outcome event from Action Type)

  • Fulfillment Completed

  • OR

  • Fulfillment Failed


Step 4 (Next rule)

IF Fulfillment Completed → Trigger shipping
IF Fulfillment Failed → Retry or alert

🧠 Simple Analogy

Think of it like a relay race:

  • 🟒 Start gun → Trigger Event

  • πŸƒ Runner runs → Action

  • πŸ” Baton pass → Business Event in Action Type

  • 🏁 Next runner continues → Next orchestration step


⚠️ Important Clarification

πŸ‘‰ Action Type does NOT trigger the first step
πŸ‘‰ It defines what event to raise AFTER execution


✅ Final takeaway

  • Business Events (top level) → Start orchestration

  • Business Events in Action Type → Continue orchestration

πŸ‘‰ They are part of the same event-driven chain, just at different stages.

Comments

Popular posts from this blog

πŸ” Dataverse + Azure Integration: Choosing Between Synapse Link and Microsoft Fabric

⚡ Example: Rate Limiting in Azure API Management

In-Process vs Isolated Process Azure Functions: What’s the Difference?