Impact Of Quarterly Patches On Oracle Fusion App Redwood Pages And Visual Builder Extensions (Doc ID 3027725.1)

Last updated on JUNE 07, 2024

Applies to:

Goal

This document describes some of the best practices for the Impact of Quarterly Patches on Oracle Fusion App Redwood Pages and Visual Builder Extensions

1) If create a new project using the 'Edit Page in Visual Builder Studio' option, then the customized section that is deployed previously is not editable. Please note, not using the original project that was used for deploying the customization.
 So question is: The previously deployed extension is now part of the page. Shouldn't that customization be editable in the new project? Why is it not editable?

2) Another scenario is after quarterly patching, let's say Oracle has included new features to a redwood page. This page was previously customized using Visual Builder. Don't we need to create a new project using the 'Edit Page in Visual Builder' option to see the latest features introduced by Oracle? We cannot use the old project that was created for customization to this page - say 6 months back - because the GIT repository for that project will not have the latest Oracle features - correct?

For the #2, what is the right way to handle quarterly patches? Do we recode our customizations in the new project? Or Will they be there already, but not editable?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.