📌 Introduction

Ever faced a scenario where a line manager gets changed after a journey is assigned—but tasks still go to the old one? 😖

Imagine assigning an onboarding task today, but by the time the task is due, the employee’s line manager has changed. Who should get the task—the old or the new manager?

Oracle Journeys now has your back! With the latest enhancement, you can evaluate the task owner and performer at the moment the task starts, not when the journey is assigned. 🎯

Let’s decode how this works and why this one checkbox can save your support team from a storm of escalation emails. 💡

---

⚙️ Setup: One Powerful Checkbox

Oracle now gives you a setting called “Evaluate task performer and owner when task is initiated”. When enabled, the task ownership is determined only when the task actually begins (not when it’s allocated).

This is particularly useful when:

• A task depends on another task’s completion 🧩
• A task has a delay duration (deferred tasks) ⏳
• A journey itself is scheduled to start in the future 📅

---

✅ Step-by-Step: How to Enable This Feature

Here’s how you can activate this logic in just a few clicks:

1. 🔍 Navigate to the Home page and click My Client Groups.
2. 🧭 Click Show More under Quick Actions.
3. 🧩 Go to Journey Templates under the Journeys Setup area.
4. 📄 Choose the journey template where the task exists.
5. ✏️ In the Tasks section, click Edit for the task you want to configure.
6. 🛠️ Go to the Advanced tab.
7. ✅ Set “Evaluate task performer and owner when task is initiated” to Yes.
8. 💾 Click Save.

🔐 Access Tip: You need the Manage Journey (ORA_PER_MANAGE_JOURNEY_TEMPLATE) privilege to access this.

---

Option to Evaluate Task Performer and Owner When Task is Initiated

---

🌍 Real-World Use Cases

Let’s break it down with scenarios where this feature changes the game:

---

🔁 1. Task Depends on Another Task

For example:

• Task 2 is dependent on Task 1.
• Task 2 performer is the line manager.
• Line manager is changed before Task 1 is completed.

Without This Setting Enabled

• Task 2 is assigned to the original line manager as soon as Task 1 is created.
• Even if the manager changes later, Task 2 stays with the original manager.
• Notification is sent only when the task is initiated—to the old manager.

With This Setting Enabled

• Task 2 is not evaluated until Task 1 is completed.
• Task performer is reassigned to the new line manager at initiation.
• Task is removed from the old manager’s view and appears in the new manager’s task list.
• Notification goes to the correct (new) manager.

---

Line Manager Owner and Performer Before Assigning

Visual flow of Task 2 going to the old line manager even after a change.

Line Manager Owner and Performer After Assigning

Visual flow showing Task 2 being re-evaluated and assigned to the updated line manager.

---

⏱️ 2. Task is Deferred with Delay Duration

For example:

• Task A has a 10-day delay from journey assignment.
• Line manager changes on Day 5.

Without This Setting Enabled

• Task A is pre-assigned to the line manager at journey assignment.
• Even after the manager changes, the task stays with the original person.
• Notification sent to the old manager when the task is activated.

With This Setting Enabled

• Task A’s performer is not determined until Day 10.
• New manager is identified at task initiation.
• Notification sent to the correct (current) manager.

---

📅 3. Journey is Deferred (Days for Initiation)

For example:

• Onboarding journey is configured to initiate 5 days after hiring.
• Tasks B and D have the line manager as the performer.
• The line manager changes on Day 3.

Without This Setting Enabled

• Tasks B and D are evaluated at the time of journey assignment.
• Assigned to the original manager, even though the journey hasn’t started yet.

With This Setting Enabled

• Tasks B and D remain disabled until the journey starts.
• At initiation, the task performer is reassessed.
• Tasks are routed to the new line manager.

---

🎯 Why This Matters

This small toggle avoids:

• ❌ Notifications going to ex-managers
• ❌ Confused task ownership
• ❌ Manual reassignments
• ❌ Escalations and ticket pile-up

✅ Instead, it ensures task ownership is always current, clean, and contextually accurate.

---

📌 Conclusion

This enhancement is a perfect example of Oracle listening to the community—yes, it came from an idea submitted on Cloud Customer Connect! 👏

The next time you’re configuring onboarding or complex task chains in Journeys, don’t forget to enable this setting. It can make the difference between a smooth experience and a manual firefight.

Stay smart, stay updated, and keep exploring #FusionPathFinder for Oracle HCM gems like this! 💎