It doesn’t feel that long since we started talking about 25B, but now its time for 25C! With Core HR being mandatory in Redwood by Release 25C, I would be lying if I said there were a significant number of new features for Core HR in 25C, but there are some features of note! Please keep in mind that Oracle will continue to roll out additional features throughout the quarter, if there are any subsequent features of note, I will do a follow up blog on these.
A lot of organisations, particularly in the public sector have been eagerly awaiting the changes to the Public Worker Search functionality. For those of you who don’t know what Public Workers Access is, it determines which employee records are returned in searches and other public-facing views. This allows for controlling the visibility of sensitive information like job codes or positions by applying user-defined criteria. 25C is the first release that brings Public Worker Access support to Oracle Search and Redwood. So what does this mean? If you need to limit employees or positions being available in Public Search due to the confidential nature of their role, now you can! It can be configured in a variety of ways including adding exclusion criteria.
In addition, Oracle have introduced the ability to export your Public Worker Access between pods. This will allow the migration of Public Worker Access configuration to be much simpler and remove any risk of human error. It will ensure that the config that has been tested in your development pod is the same as what is deployed in Production.
There are a lot of Journey related features in this release. One I particularly like is quite a simple change but I think it will add significant value. The ability to easily schedule recurring Journeys will make Journey administration a lot easier. The flexibility of being able to chose the frequency, but also limit the number of times the Journey is assigned makes this such a great addition.
The final Journey feature that I want to highlight is the ability to embed Multi Agents into Guided Journeys. This will allow a variety of different AI Agents to be embedded into pages with ease. Added AI Agents to pages is done via Guided Journeys and this new functionality makes it much easier. This is the perfect time for this improvement when we’re all prepping for the introduction of AI Agent Studio to speed up the process of creating AI Agents!
The other area of Core HR with significant changes are within the Workforce Structures workspace. There are a number of new pages that have moved over to Redwood, including the Legal Entity HCM Information and Legal Reporting Unit HCM Information pages. Additionally Oracle have given more flexibility in adding extra attributes on the summary of changes page for all Workforce Structure changes. These fields can be added in via VBS to allow for the easy review of changes to fields that are important to your organisation.
As mentioned earlier, Oracle plans to roll out new features in Core HR later this month. Should these updates turn out to be noteworthy, I’ll publish a refreshed blog post. Additionally, keep an eye out for upcoming posts that will cover other modules within Fusion for Release 25C!
Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines
K8 Mead 
3 thoughts on “Oracle HCM Cloud Core HR 25C”