Redwood page templates in Oracle Visual Builder are designed for reusability and encapsulation. The components within a template, such as a primary action button, are not directly accessible from the page that uses the template. Instead, the template exposes specific, predefined events. The button inside the template is wired to fire a primaryAction event. To define what this button does, you create an action chain on the page and map it to this primaryAction event exposed by the template. This decouples the page's logic from the template's internal structure, which is a core design principle.

A. You cannot. The functionality is determined by the original template

This is incorrect. Templates are designed to be customized by the pages that consume them; otherwise, they would have very limited utility.

B. Create an onAction action chain on that button

This is incorrect because you cannot directly select or modify components encapsulated within a page template from the page designer's context.

C. Remove the existing button from the template and add your own

This is an improper approach that breaks the connection to the template, defeating the purpose of using it for a consistent layout and future updates.

1. Oracle Visual Builder Documentation - Develop Applications with Oracle Visual Builder: In the section "Work with Page Templates

" the subsection "Add an Event Listener to a Page Based on a Template" explicitly states: "When you create a page from a template

you can add an event listener to the page to trigger an action chain when an event on the template occurs. For example

you can add an event listener that listens for the template's primaryAction event and triggers an action chain to save data." This directly supports answer D.

Source: Oracle Help Center

Develop Applications with Oracle Visual Builder

Release 24.04

Part Number F82535-02

Chapter: "Work with Page Templates".

2. Oracle Visual Builder Documentation - Page Model Reference: The documentation on page templates describes how they define custom events that can be handled by the consuming page. The primaryAction event is a standard event exposed by Redwood templates for this exact purpose. The page's event listener mechanism is the designated way to subscribe to and handle these template events.

Source: Oracle Help Center

Develop Applications with Oracle Visual Builder

Release 24.04

Part Number F82535-02

Chapter: "Understand the Page Model".