1z0-1114-23 Oracle Redwood Application 2023 Developer Associate Question and Answers

The Pattern Book is a collection of templates and patterns that provide guidance and best practices for developing Redwood applications. It includes a template introduction that explains the purpose and usage of each template, a pictorial representation of data that shows how to visualize data in different scenarios, and composites and components that describe the common elements and interactions of Redwood UIs .

References: : Oracle Redwood Pattern Book : Oracle Redwood Design System

A transactional page template is a type of page template that supports creating, updating, or deleting data in Fusion Cloud Apps. It usually consists of a form or a table with input fields, buttons, and validations. Some examples of transactional page templates are Gantt page template, Guided process page template, and Advanced create and edit page template. A foldout layout page template is not a transactional page template because it does not support data manipulation. It is a type of page template that displays information in a collapsible panel on the side of the page.

References: : Transactional Page Templates in Redwood Pattern Book : Foldout Layout Page Template in Redwood Pattern Book

The two available positions for drawers in the Data Grid pattern are start position and end position. These are the positions where the drawers can slide out from when triggered by an action on the Data Grid. The start position is on the left side of the Data Grid, while the end position is on the right side of the Data Grid.

References: : Data Grid Page Pattern in Redwood Pattern Book

This question tests your knowledge of how to share your AppUI extension in Visual Builder Studio with another developer for testing purposes. The correct answer is C, because you can choose the Share option from the menu in your workspace editor to generate a URL that you can send to another developer who can access your extension in read-only mode. The other options are incorrect, because they are not the best ways to share your extension for testing purposes. Here is why:

• Option A is incorrect, because creating a shared workspace with another developer would allow them to edit your extension as well as view it, which might not be what you want.
• Option B is incorrect, because clicking the Publish button in your workspace would push your changes to Git and also start a merge request, which might not be what you want if you are not ready to merge your changes yet.
• Option D is incorrect, because pushing your changes to a shared branch before pushing it to Git would require you to create another branch and also ask the other developer to switch to that branch in their workspace, which might be more complicated than simply sharing your URL.

References: [Sharing Your Workspace], [Publishing Your Changes]

This question tests your knowledge of the dialog message components that are available in Redwood, which are used to interrupt the user and force them to make a decision. The correct answer is A, C, and E, because these are the three dialog message components that are available in Redwood. The other options are incorrect, becausethey are not dialog message components, but banner message components or page templates that can be used in different contexts. Here is a brief description of each dialog message component:

• oj-sp-message-dialog-destructive: This component is used to display a dialog message that warns the user about an irreversible action that will delete or destroy data. It has a red header with an icon and a title, a body with a message and an optional description, and two buttons for canceling or confirming the action.
• oj-sp-message-dialog-general: This component is used to display a dialog message that informs the user about an action that requires their confirmation or input. It has a blue header with an icon and a title, a body with a message and an optional description or input field, and one or more buttons for canceling or completing the action.
• oj-sp-message-unsaved-changes: This component is used to display a dialog message that alerts the user about unsaved changes that will be lost if they navigate away from the current page. It has a yellow header with an icon and a title, a body with a message and an optional description, and two buttons for discarding or saving the changes.

References: [Redwood Dialog Messages], [oj-sp-message-dialog-destructive], [oj-sp-message-dialog-general], [oj-sp-message-unsaved-changes]

The best way to achieve this is to have Tammy create a new workspace based on Jim’s workspace. A workspace is a private copy of the code that you can work on without affecting other developers. You can create a new workspace from an existing one by selecting the option “Create Workspace From” in Visual Builder Studio. This will copy allthe changes from the source workspace to the new one, allowing Tammy to continue the work Jim did.

References: : Workspaces in Visual Builder Studio : Creating Workspaces in Visual Builder Studio