Clarification on Oracle’s Definition of Configuration vs. Configuration Extension in Redwood
Summary:
Is duplicating a Redwood layout to reorder fields considered configuration or configuration extension? Does Oracle recommend duplicating the layout for all implementations?
Content (please ensure you mask any confidential information):
Hello Oracle Community,
I would appreciate clarification on Oracle’s official definition of Configuration vs. Configuration Extension.
Specifically, we would like guidance on the following:
1. How does Oracle define Configuration Extension in the context of Fusion Sales / Redwood?
2. If we duplicate a delivered Redwood layout solely to:
• Reorder fields
• Hide or expose existing standard fields
• Adjust section placement
• Assign the layout to a specific role
would Oracle consider this: