Redwood for Global HR – What Do you Need to Know?

As you will know, Redwood is mandatory for Global HR from Release 25C, so now is time to make the move!  The first question I am asked is will there be a replacement for Person Management? I’ll be honest with you, I love Person Management! The good news is that Oracle have confirmed that there will be, the ‘HR Activity Centre’. The date for release hasn’t been confirmed, but it is coming. Oracle have caveated that it won’t be a like-for-like replacement, but it will be a centralised location for transactions rather than having to go to different quick actions.

Oracle massively ramped up the number of Global HR features available within Redwood in 2024, so the majority of features are already available to you right now. As the picture above shows, if you’re not currently using autocomplete rules and have no requirement for creating unsupported defaulting rules, you can move to Redwood for Global HR right now. If you do have a requirement to default in data using rules, the amount of rules for defaulting data available will be significantly increased in 25B. This doesn’t mean wait for 25B though, it’s important that if you haven’t started, to start the switch in a non-production pod. Using a dedicated Redwood pod is always my recommended approach as it won’t impact on quarterly regression testing or issue resolution, due to the pod not matching what is currently in Production.

Global HR differs slightly to other modules when moving to Redwood. There are the usual steps, enabling Oracle Search, Updating Custom Security Roles; Reviewing and Migrating Personalisations using the Personalisation Helper Tool and Switching on the Redwood Flows via Profile Options. For Global HR, there are two additional prerequisites. Firstly, to be able to use the Redwood pages for Termination and / or Resignation, you must have migrated to Termination V3. To be able to use the Redwood page for Seniority Dates, you must be using Version 3 of Seniority Dates. So what happens if you’re not using one or both of the prerequisite versions? For terminations and resignations, you won’t be able to use the Redwood page. For Seniority Dates, there is an alternative, you can manage the dates via the Redwood Work Relationship page. If you want the full Redwood experience, I would recommend making the move to the latest versions of both Termination and Seniority Dates. My other recommendation is to migrate the V3s now, not after you’ve moved to Redwood. This will make the process more straightforward and therefore easier.

So what are my top tips? The Redwood ‘Bible’ only lists the key flexfields the need switching on. Check the What’s New Documents for all related modules for all the historic Redwood updates. Have you seen the Feature Listing Report on the Cloud Readiness website? From here you can download every upgrade since 2023 for every Fusion module in a handy spreadsheet. You can then use filters to find all the Redwood features for a given module.

A lot of users have reported issues with flexfields whilst testing Redwood. If this happens, redeploy the flexfields and make sure all flexfield personalisations have been migrated. Likewise if you’re having issues with pages, firstly ensure that the appropriate profile options for Oracle Search are switched on. If that doesn’t work, ensure custom roles have the correct privileges.

The Redwood Personalisation Tool is extremely helpful. Whilst it can’t migrate all personalisations, it will migrate some of them and reduce the amount of manual personalisations that will need to be applied. I would always recommend only using it in Migration mode for a small subset at a given time. Preferably one flow at a time. This gives you the chance to review the personalisations and make corrections more easily. Additionally once the tool has been used to migrate a flow, you can’t use it again for that specific flow. Even if a newer version of the tool provides more migration options within that flow.

Finally, use the new Activity Centres. Within the Global HR space, there is currently one for employees and one for line managers. These are a one stop shop for users to access all their and their team’s HR records and carry out their tasks. As I said earlier, one for the HR Team to replace Person Management is coming, so watch this space! Check out my earlier blog on Activity Centres here.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines.

Updated Redwood Timelines

Oracle have made a slight change to the Redwood Timelines that were announced in August. Whilst it is not a significant change, there has been a separation of the deadlines for moving timecards to Redwood.

Those who complete timecards on a desktop / laptop, will still need to migrate to Redwood timecards by release 25A. The change is for those who complete timecards on a mobile device, have a little longer to make the move to Redwood. This has been pushed out to release 25B to give more time to make the necessary changes.

All other dates remain the same. The initial focus is Redwood Journeys and Redwood Timecards for desktop users. These are all mandatory in release 25A. The first deadline in the Procurement area is Self Service Procurement in release 25C.

About the Author:

Kate Mead is an Oracle-certified HCM Consultant and Solution Architect at Version 1 with 14 years of experience in Oracle HR and Payroll systems, including 7 years with Oracle HCM Cloud. She has worked across implementation projects and managed services, has a sound knowledge of UK Payroll legislation and — before becoming a consultant — was an HR Manager.

If you have any questions or would like more information on how Version 1 can help you realise the full potential of your Oracle Cloud instances, please contact her at kate.mead@version1.com

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines

Oracle Cloud Redwood Customization Helper Tool

Today is the day! Oracle has released details of how to run the Redwood Customization Helper Tool. So what is it? It is a new tool that reports on your Responsive UX page personalisations that have been made in either Page Composer or Transaction Design Studio.

Page Composer Customizations Output

The tool outputs a JAR file which indicates which personalisations are supported in your current version of Visual Builder Express (VB Express) Business Rules. What’s even more exciting than the tool providing details of your personalisations to make the move to Redwood easier? Well, the tool also offers the option to migrate supported personalisations to your Redwood environment! It might not be quite as manual as we originally thought.

HCM Experience Design Studio Rules Supported for Migration

The above table lists all of the HCM Design Studio Rules which have the potential to be migrated using the Redwood Customization Helper Tool. Whilst not all functionality can be migrated, this is a massive improvement on what was originally communicated about the move from Responsive UX to the Redwood UX.

One key point to note is that the Customization Tool does not work with Single Sign On (SSO) accounts. If your Production pods are SSO only, you may want to run it against a non-prod pod where SSO is optional, providing all of the personalisations are present.

The second point of note is that you have to download an .exe file for it, so if your organisation has tight rules about what you can download, this may cause an additional complication. If you can obtain permission to download the file, it is definitely worth it.

Redwood Customization Helper Tool Forum on Customer Connect

The final piece of information that I want to highlight is that Oracle has also created a new forum area on Customer Connect as well. This will make it easier to raise any questions relating to the new tool. If you add a tag of ‘Redwood’ the core team at the Oracle Centre of Excellence will pick up the query and answer it more quickly.

About the author:

Kate Mead is an Oracle-certified HCM Consultant and Solution Architect at Version 1 with 14 years of experience in Oracle HR and Payroll systems, including 7 years with Oracle HCM Cloud. She has worked across implementation projects and managed services, has a sound knowledge of UK Payroll legislation and — before becoming a consultant — was an HR Manager.

If you have any questions or would like more information on how Version 1 can help you realise the full potential of your Oracle Cloud instances, please contact her at kate.mead@version1.com

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines