Redwood Enabled by Default for Journeys

Starting with Update 25C, Redwood journey pages will be enabled by default, and the Responsive Checklist Tasks, Onboarding, and Allocated Checklist pages will no longer be available. Additionally, Oracle Search for Journeys will also be enabled by default.

These are a few advantages of this enhancement:

• Modern and Intuitive Experience: Redwood pages offer a streamlined, user-friendly interface.

• Improved Efficiency and Performance: Built with the Redwood toolset, the new pages reduce the number of clicks and enhance overall performance.

• Consistent Application Flow: Benefit from a cohesive user experience across the application.

• End of Support: Responsive Checklist Tasks, Onboarding, and Allocated Checklist pages will no longer be supported.

• Automatic Enablement: The site-level profile option ORA_PER_JOURNEYS_ENABLED will be set to Y by default.

Journeys on the Home Page

Users can quickly and easily access Redwood journeys from a single place by using the Journeys app.

Steps to Enable

To enable Oracle Search for journeys, refer to this playbook: How do I enable Oracle Search for journeys?

If you want to, you can disable the ORA_PER_JOURNEYS_ENABLED profile option (set to N) for Redwood journeys. For more information, see the How do I enable a profile option? topic.

You need to configure security to use this feature. See the Access Requirements section.

Key Resources

For more information, refer to these resources:

• Implementing and Using Journeys guide.

• Checklists and Onboarding to be Replaced with Journeys in Update 25C feature in the 25B Global Human Resources What's New.

• Security Reference for HCM guide.

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Access Requirements

If you use predefined roles, no action is necessary. However, if you use custom versions of these roles, you need to add journeys related privileges to your custom roles.

Add these privileges to your custom roles:

• For the custom Employee role, add the ORA_PER_ACCESS_JOURNEY_BY_WORKER (Access Journey by Worker) privilege.

• For the custom Line Manager role, add the ORA_PER_MANAGE_JOURNEY_BY_MANAGER (Manage Journey by Manager) privilege.

• For the custom Human Resources Specialist role, add the ORA_PER_MANAGE_JOURNEY_BY_HR (Manage Journey by HR) privilege.

See the Release 13 Oracle Human Capital Management Cloud Security Upgrade Guide on My Oracle Support (Document ID 2023523.1) for instructions about implementing new functions in existing roles.

For information about existing security privileges, refer to the Security Reference for HCM guide on Oracle Help Center.