You are designing the UI to display information about a product and are asked to use the card layout, such that:
* The card layout summarizes the available information about a product in a visually compact manner.
* The card layout is used as an entry point from where users can access additional details.
Which card layout is suitable for the above requirements?
The Object Card layout is suitable for displaying information about a product and using it as an entry point from where users can access additional details. The Object Card layout consists of a header with an icon and a title, a body with one or more fields or actions, and a footer with optional actions or indicators. The Object Card layout summarizes the available information about a product in a visually compact manner and allows users to perform actions on it or navigate to more details. Therefore, option A is the correct answer. Reference: [Object Card Layout], [oj-sp-object-card]
You created a page based on the Foldout layout template.
How do you ensure that your customer can access it from a mobile phone?
The easiest way to ensure that your customer can access your page from a mobile phone is to do nothing. Responsive behavior will render the page properly on the device. This is because Redwood design system is built with responsiveness in mind, meaning that it adapts to different screen sizes and orientations automatically. The Foldout layout template, for example, will collapse the foldout panel on smaller devices and show it as a modal dialog when triggered.
By design, dialog messages interrupt the user and force them to make a decision.
Which three dialog message components are available in Redwood? (Choose three.)
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, because they 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.
The Redwood template your page is based on has a primary action button.
How do you control what it does?
The primary action button is a UI component that represents the main action that the user can perform on a page. It is usually located at the top right corner of the page and has a prominent color and style. The primary action button is defined by the Redwood template that your page is based on, and its functionality is determined by an action chain mapped to the template's primary action event at the template level. You can create or modify this action chain to control what the primary action button does on your page .
Jane created an AppUI extension in a workspace. She wants Troy to test it before she pushes it to Git.
How can she achieve this?
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.
