Intelligent Order Management Core Concepts

 This is a core concept in orchestration inside

Dynamics 365 Intelligent Order Management — and once you see the linkage clearly, everything else (flows, providers, execution) becomes much easier.

---

🧠 Big Picture (End-to-End Flow)

Business Event → Orchestration Rule → Action Type → Provider Action → Execution (Power Automate)

Each piece has a specific role 👇

---

🔷 1. Business Events (Trigger layer)

👉 Business Events = “Something happened”

Examples:

• Order created

• Line updated

• Fulfillment completed

✔ These are generated inside IOM or external systems
✔ They trigger orchestration

---

🔷 2. Orchestration Rule (Decision layer)

👉 This is where logic is defined:

• WHEN event occurs

• IF conditions match

• THEN perform action

Example:

If Order Created → Trigger fulfillment

---

🔷 3. Action Type (Template layer)

👉 Action Type = “What kind of action is this?”

It defines:

• Category of action (e.g., Fulfillment, Payment, Transformation)

• Expected inputs/outputs

Think of it as a blueprint

Examples:

• Send to Fulfillment

• Reserve Inventory

• Transform Order

---

🔷 4. Provider Action (Execution mapping)

👉 Provider Action = actual implementation of Action Type

• Linked to a Provider

• Backed by a Power Automate flow

Examples:

• “Send Order to Warehouse API”

• “Call ERP system”

✔ This is where real work happens

---

🔷 5. Provider (System connector)

👉 Provider = external/internal system

Examples:

• ERP

• Warehouse

• Payment system

✔ Provider Action belongs to a Provider

---

🔗 How they are linked (step-by-step)

Step 1

Business Event occurs
➡️ “Order Created”

---

Step 2

Orchestration rule listens to that event
➡️ Decides what to do

---

Step 3

Rule selects an Action Type
➡️ e.g., Fulfillment

---

Step 4

IOM finds the Provider Action mapped to that Action Type
➡️ e.g., Send to Warehouse

---

Step 5

Provider Action triggers a Power Automate flow
➡️ Executes actual integration

---

📦 Real Example

Business Event:
Order Created

↓
Orchestration Rule:
If order created → send to fulfillment

↓
Action Type:
Send Sales Order to Fulfillment

↓
Provider Action:
Warehouse Fulfillment API Call

↓
Execution:
Power Automate flow runs

---

🧩 Simple Analogy

Component	Meaning
Business Event	Doorbell rings 🔔
Orchestration	Decide what to do 🤔
Action Type	“Call delivery service” 📦
Provider Action	Actual delivery company 🚚
Provider	The company itself

---

⚠️ Important Points

• One Action Type can have multiple Provider Actions

• Provider Action = bound to specific system

• Business Events do not execute logic directly

• Orchestration is the brain

---

✅ Final takeaway

👉 The linkage is:

• Business Event → triggers process

• Orchestration Rule → decides action

• Action Type → defines what kind of action

• Provider Action → executes it via provider

🧭 Where everything is configured (UI Mapping)

---

🔷 1. Business Events (Trigger)

📍 Path:

• IOM → Orchestration → Business events

👉 Here you:

• View available events

• Enable/disable events

• Understand what triggers orchestration

✔ Example events:

• Order created

• Order line updated

---

🔷 2. Orchestration Rules (Logic)

📍 Path:

• IOM → Orchestration → Policies (or Orchestration rules)

👉 Here you configure:

• Conditions (IF)

• Actions (THEN)

✔ Example:

IF Order Created
THEN Send to Fulfillment

---

🔷 3. Action Types (Template)

📍 Path:

• IOM → Providers → Action types

👉 Here you define:

• Type of action (Fulfillment, Payment, etc.)

• Input/output schema

✔ Think of this as:

“What kind of operation is this?”

---

🔷 4. Providers (System)

📍 Path:

• IOM → Providers

👉 Represents:

• External systems (ERP, Warehouse, Payment)

✔ Example:

• Warehouse system

• ERP system

---

🔷 5. Provider Actions (Execution)

📍 Path:

• IOM → Providers → Select Provider → Actions

👉 Here you:

• Map Action Type → Actual implementation

• Link to Power Automate flow

✔ This is the most important configuration

---

🔷 6. Power Automate Flow (Backend execution)

📍 Path:

• Open Microsoft Power Automate

👉 Each Provider Action:

• Has a flow behind it

• Executes API / business logic

---

🔗 End-to-End UI Flow

Business Events (Orchestration menu)
        ↓
Orchestration Rules / Policies
        ↓
Action Type (Providers section)
        ↓
Provider
        ↓
Provider Action (linked to flow)
        ↓
Power Automate Flow executes

---

🎯 Example (UI + Logic together)

Scenario: Send order to warehouse

1. Business Event

   • Order Created

2. Rule

   • IF Order Created → Trigger Fulfillment

3. Action Type

   • Send Sales Order to Fulfillment

4. Provider

   • Warehouse Provider

5. Provider Action

   • “Send to Warehouse API”

6. Flow

   • Calls warehouse system

---

⚠️ Where people usually get stuck

• Action Type created but not mapped to Provider Action

• Provider Action exists but no flow linked

• Rule created but wrong event selected

• Flow exists but connection reference missing

---

✅ Final mental model

👉 In UI terms:

• Business Event → What happened

• Rule → What should I do

• Action Type → Type of work

• Provider Action → How to do it

• Flow → Actually does it