Why the transition from ADF to Redwood: Fusion CX Sales and Service

Why the transition from ADF to Redwood: Fusion CX Sales and Service

With Redwood being at the forefront of innovation within Fusion CX Sales and Service, I was excited to attend the Customer Connect: CX – The Future of Oracle CX Sales & Service: Guidance on the Move to Redwood. From attending that session, I wanted to share a few key takeaways, particularly how I resonated as an implementor, and hopefully start a discussion with the community.

One of the main highlights was the roadmap around the Redwood transition. The team clarified that ADF will no longer be supported past 27A, which reinforces the importance of planning our migration paths early and how Oracle has created a way to empower businesses for a smooth transition to redwood through its Redwood Accelerators. This is exciting as it takes some of the pressure of migrating, however, why would someone want to migrate other than ADF pages not supporting past 27A? In my opinion, there are two reasons are cross-application cohesiveness and data powered performance.

Cross Application Cohesiveness

As someone who has a deep appreciation for good user experience (UX), I believe Redwood allows us to implement an adaptive solution while remaining united to different modules that make up fusion and even beyond. In the past, I’ve been asked what makes Oracle Fusion Sales and Service stand out from its competition and my answer always lies in its ability to provide users with a full suite, and consistent look and feel across CX, HCM, and ERP. From an implementation standpoint, these modules can be turned on with a few simple clicks. While this typically does not mark the completion of an implementation, the capability to activate these modules so effortlessly sets Fusion apart from many other systems.

Cohesiveness now extends beyond Fusion, as Oracle is releasing Redwood versions of previously separate applications, such as Oracle Field Service Cloud and Oracle Configure Price Quote. But what happens when our users need more than what is provided in the Out of the Box (OOTB)? Redwood's design system ensures applications remain visually consistent, even as custom requirements are added. I believe that Oracle’s drive to enable customization while providing a consistent look and feel is a true testament to their united long-term vision.

Data Powered Performance

Redwood is leveraging data at the forefront of artificial intelligence and performance. By utilizing Redwood, businesses can take advantage of the different categories within AI such as Predictive AI, Generative AI, and AI Agents. AI facilitates features including guided workflows and intelligent recommendations. One example that oracle highlighted was how AI can streamline tasks such as initiating the sales process from upstream activities such as generating an opportunity from a quote. But how we interact with data goes beyond workflows as we can get additional data insights. Through these insights users will be able to receive patterns and trends analyzed through Redwood. One interesting thing I have noticed while working on redwood vs ADF is speed! Fusion has come a long way, the application has only gotten faster, and faster. With Redwood, we can now see faster searches that from my experience match or exceed that of what is in workspace. These are all things Oracle is continuing to work on, and I am excited to see the value they bring to our clients.

Final Thoughts

My main takeaway from the call is that we are in a hybrid phase: Classic and Redwood will coexist for now, hence leveraging both is important for user support. I'm eager to see Oracle's ongoing improvements that will support our transition to Redwood.

Curious to hear how others are preparing for the transition and what features you’re most excited about coming to Redwood.

Featured in Oracle University:
https://community.oracle.com/ou/discussion/22293/why-the-transition-from-adf-to-redwood-fusion-cx-sales-and-service#latest