What in the purpose of the Track Target Position Netting in the Advanced Settings of the Full Editor?
Options:
A.
To make the highlighted section of the screen smaller or bigger using pixel precision
B.
To redirect a guide back to the Help widget
C.
To ensure that a tip stays on the target element if the element's position moves when the user scrolls
Answer:
C
Explanation:
Explanation:
The Track Target Position Netting is a feature in the Advanced Settings of the Full Editor that allows you to adjust the behavior of the tip position relative to the target element. The target element is the element in the application that the tip is pointing to or highlighting. The tip position is the location of the tip on the screen. The Track Target Position Netting feature has three options: None, Fixed, and Dynamic. None means that the tip position is fixed on the screen and does not move with the target element. Fixed means that the tip position is fixed relative to the target element and moves with the target element. Dynamic means that the tip position is dynamic and adjusts to the target element’s position and size. The purpose of the Track Target Position Netting feature is to ensure that the tip stays on the target element if the element’s position moves when the user scrolls or resizes the window. This feature can help to improve the user experience and avoid confusion or misalignment of the tip and the target element. You can configure the Track Target Position Netting feature in the Advanced Settings tab of the Full Editor, by selecting the option from the drop-down menu. References:
By using OGL, you can disable page elements that are not relevant or distracting for the user during a guide. This feature is called Page Masking and it allows you to create a transparent overlay that covers the entire page except for the elements that you want to highlight or interact with. Page masking can improve the user experience and focus by hiding unnecessary or confusing elements. You can configure the page masking settings in the OGL editor, such as the opacity, color, and border of the overlay. You can also use the Exclude Elements option to select the elements that you want to exclude from the page masking. Page masking can be applied to any step type, not just hot-spots. References: Creating OGL Content Course, Enhancing OGL Content Course, [Oracle Guided Learning Content Developer Foundations Associate Rel 1 Exam]
Question 26
What is the purpose of Display Groups?
Options:
A.
To manage how content in the Help panel is displayed, sorted, and categorized
B.
To create content that is displayed in Fusion applications only while in development
C.
To display the content in the Fusion application under specific modules
Answer:
A
Explanation:
Explanation:
Display groups are a feature of Oracle Guided Learning that allow content developers to organize and present their content in the Help panel, which is a widget that appears on the right side of the Fusion application. Display groups can be used to group content by module, process area, or any other suitable category. Display groups can also be used to sort and filter the content based on user preferences, roles, or permissions. Display groups can have a name and an icon, and can be created, edited, or deleted in the Display Group Manager, which is accessible from the Content tab in the OGL Console. Display groups can also be assigned to content items by dragging and dropping them in the Display Group Manager, or by selecting them from the drop-down menu in the Content Editor. References: Display Groups, Creating Display Groups, Adding Content to Display Groups
Question 27
Where and to whom in a guide with the Published status visible?
Options:
A.
Only in the production environment to end users
B.
In the development and production environments
C.
Only in the development environment to administrators
Answer:
B
Explanation:
Explanation:
A guide with the Published status is visible to both end users and administrators in the development and production environments. The Published status indicates that the guide is ready to be used by the end users on the application. However, the guide can still be edited and updated by the administrators in the OGL console, and the changes will be reflected in both environments. The development environment is a sandbox where the administrators can test and preview the guides before publishing them to the production environment, which is the live application where the end users access the guides12. References: