5 OGL Console Left Panel

My Content

The My Content section in the left panel of the OGL Console provides an overview of all content items in the account (i.e. process guides, messages, beacons, etc.).

Select Content () to display all of the current content items that you have created or copied from a library, such as Use Cases. These content items will appear in the main content page to the right and will include all content items that are in Draft, Published, or Inactive status. These content items can be sorted and/or filtered to allow for more efficient browsing.

Sorting and Filtering Content Items

To sort your content items, select the Sort () dropdown menu and choose a sorting option.

To filter your content items, use the Filters () panel on the right side of the page and select from any of the available filtering categories and options to narrow the list of content items displayed.

Note:

If the Filters panel is not displayed, be sure to activate it by selecting button located at the top of the My Contents page.

Below are all of the available categories with which you can can filter content items:

Archived Content

Content items that you delete are not permanently deleted and are simply moved to Archive. Select Archive () to display all items that have been deleted in the account. These content items can also be sorted and filtered for more efficient browsing, as shown above.

To recover any archived items and move them back to your Content, select the Recover () button on the content item you wish to restore.

Settings

Accessing the Interface

1. On the left navigation panel, select Settings.
   

Application

Accessing the Interface

1. On the left navigation panel, select Settings.
   

Understanding the Interface

The Application tab:

Legend	Description	Additional Information
1	Application tab	n/a
2	Application Name	This is the application name, displayed next to the account name
3	Application type	Fusion = This appID is linked to a Fusion application Other = Any application that is not Fusion (i.e. Salesforce)
4	Available Products for Content Display in the OGL Libraries	The products selected in this list will determine which content items will display in the content libraries, including Uses Cases, Base Guides, and Business Process Training libraries.
5	Default Editing URL	This is the default editing URL for new item creation. Note, setting the URL in this field does not replace/update the editing URL for existing items.
6	User Roles	Indicates if the user roles are being collected by OGL for reporting in analytics. To have identifiable usernames enabled for your organization (subject to legal requirements being met), please create a service request on My Oracle Support.
7	Player Authentication	This setting allows administrators to restrict OGL content to only display for end-users who are properly authenticated in the host application. If enabled, end-users must be authenticated in the host application in order to see OGL content.
8	Application ID	This is the unique application ID for the account.
9	Deployment	Indicates OGL deployment methods. Please select only the applicable options for the appID
10	Default Language	Indicates the set default language for the appID. (i.e. if the default content language is French, and French has been selected in the field, this indicates to OGL that French = Generic Language (fr = --)) Note: This is not the language of the OGL Console, but that that of the content items in the application
11	Save button	Allows you to save the changes made to the configuration. Note: The Save action applies to the Application, Editor, and Playback tabs. The Save button on the Domains tab only applies to that and not the previously mentioned tabs

The Domains tab - General

Legend	Description	Additional Information
1	Domains tab	The Domains tab contains OGL configuration settings for Fusion.
2	Configuring OGL in Fusion	Description: Oracle Fusion applications can be configured to automatically integrate with OGL. To set up this integration, you will need to copy the Oracle Guided Learning Application ID (OGL AppId) and the OGL Server URL, both provided below, into the corresponding fields in the Fusion OGL Integration page. This will make your OGL content visible in your Fusion application.
3	OGL App ID	Identifies the application ID for use in OGL configuration, enter the ID into the Application ID field in Fusion
4	OGL Server URL	Identifies the server URL for the application ID, enter the URL into the relevant field in Fusion
5	Copy button	Allows you to easily copy the application ID or the server URL to the clipboard.
6	Add a Domain	Domains represent a location, usually an application, where Guided Learning content will be used. Domains are defined by a URL (e.g. https://guidedlearning.oracle.com). To add a domain, select the + New Domain button, enter the URL of the application and the name you would like to associate with that application. Enter any other required information and save.
7	New Domain button	Allows you to define a new domain where OGL will be enabled
8	Hosts section	If there are domains defined, they will all be listed in the hosts' section in the Domains tab

The Domains tab - Add/Edit a Domain

Table 5-1 Domains General Tab

Legend	Description	Additional Information
1	Name	Defines the name of the domain (.i.e. Development / Testing / User Acceptence Testing / Production )
2	URL	Identifies the domain URL (i.e. www.myapp-uat.com)
3	Environment	Determines if OGL will show in Development mode (shows all guides) or Production mode (shows published guides only)
4	Settings - Enable OGL	Determines if OGL will be enabled/disabled for the domain.
5	Settings - Enable Report	Determines if analytics reporting is enabled/disabled for the domain. Disable this only for implementations in which there is extreme sensitivity to internet traffic and no need for reporting data.
6	Settings - Show Launch Widget	Determines if the OGL help Widget will be shown on the domain or hidden. For implementations with popups or iframes from different domains, this allows the Launch Widget to be hidden (or shown) for a given domain so that multiple Launch Widgets are not showing simultaneously.
7	Enable User Name Capture	Determines whether OGL will capture user names from the host application to be displayed in analytics and reports. Note: Please check with your regional/local user privacy laws and/or regulations and your organization's policies on user privacy before enabling this setting.
8	Set Accessibility Shortcuts	To override the default Keyboard Shortcuts (See Accessibility section of the User Guide), select a shortcut from the dropdown and enter the desired keystroke to activate it.To disable a shortcut, select it and save it with a blank keystroke field.
9	Remove	Removes the domain and associated settings
10	Enabled	Determines if the domain is enabled/disabled
11	Save Domain	Saves the domain configuration Note: The Save Domain button only applies to the domains tab. The Save action on the Application, Editor, and Playback tabs applies only to the Application, Editor, and Playback tabs.

Note:

The screen below indicates that there is a lack of sufficient privileges to Edit Cloud Configuration, request your OGL Admin for access or to make the necessary updates

The Editor tab:

Legend	Description	Additional Information
1	Editor tab	The Editor tab contains settings that can be set for the editor at the application level. You can override these settings at item level through the OGL Full Editor. Note: Set these preferences per your governance and style guide.
2	Next Button Text	Sets the custom text to display for Next button (i.e. Proceed / OK)
3	Last Next Button Text	Sets the custom text to display on the button on the last step of the guide (i.e. Close / Finish!)
4	Hide Next Button	Sets the Next button to hidden by default.
5	Hide Close Button	Sets the Close X button to hidden by default.
6	Hide back Button	Sets the Back button to hidden by default.
7	Hide Steps Count	Sets the Step Count label to hidden by default.
8	Tip Width	Sets the default Tip Width in pixels (i.e. 280.
9	Hide Highlight	Sets the default Highlight setting for all item tooltips to Hidden.
10	Highlight	Sets the Highlight for tooltips, available options are: Border and Overlay Border Overlay

The Playback tab:

Legend	Description	Additional Information
1	Playback tab	The Playback tab contains the OGL Help Widget settings for both development and production. Note: Development would have the same settings as Production by default, in case you need different settings in Development, override the Production settings. If you change only Production settings that would be defaulted to Development as well.
2	Global Image Capturing	Enable or disable the Global Image Capturing which helps in capturing the images used for Job Aids, Simulations and Videos.
3	Job Aids (Development/Production)	Enable or disable the job aids (step guide) icon in the help widget.
4	Show Images (Production)	Display images in step guides (if step guide is enabled) and in PDF files or in guide export.
5	Step Guide (Development/Production)	Display video presentations (video preview of a guide) in job aids (if job aids is enabled) and in guide export.

The Embed Code tab:

Legend	Description	Additional Information
1	Embed Code tab	n/a
2	JavaScript API Documentation Reference	https://docs.oracle.com/en/education/oracle-university/guided-learning/ogl-faq/administration.html#GUID-9059C5AB-B0D4-4A0B-B049-28B6274AD54C
3	Guided Learning JavaScript Embed Code	n/a
4	Copy Code	n/a

Custom Roles

To work with Simple Conditions, OGL now utilizes the Custom Roles setting in the OGL console. The OGL roles must be set up as per the roles set in your OGL Fusion embed or Javascript.

Click here to download a list of Role mappings.

In the OGL Role Name field, enter the Role Name.

In the Application Role Value field, enter the Role Value.

Accessing the Interface

1. Go to the OGL console.

2. On the Main Navigation Menu, select Settings > Custom Roles.
   

   The Custom Roles interface is now displayed.

Understanding the Interface

Legend	Name	Comments
1	Search Box	Provides dynamic search functionality.
2	Cancel Search	Cancels the search for roles.
3	New Role button	Adds a new empty line to the list.
4	OGL Role Name field	In the OGL Role Name field, enter the Role Name. (This is the Role name for your role and will be displayed in the item activation condition.) Note: The name field cannot be empty, and duplicate values and special characters are not allowed.
5	Application Role Value field	In the Application Role Value field, enter the Role Value. (This is the value of the role as defined in your OGL JavaScript, OGL Custom JavaScript for Fusion Embed, or in the OGL Standard Roles table.) Note: The value field cannot be empty; duplicate values and special characters are not allowed( i.e., whitespace). Lets say your JavaScript (including Custom) contains lines similar to the ones below: Lets say your JavaScript (including Custom) contains lines similar to the ones below: if(#{securityContext.userInRole['ORA_PER_EMPLOYEE_ABSTRACT']}){ user_role+='|emp|'; ORA_PER_EMPLOYEE_ABSTRACT is the role code in Fusion, emp is the OGL reference for that role code, and becomes the value you enter in the value field in the User Roles interface. If you have set up role mapping in Fusion Embed and have used the spreadsheet provided in the link above, then when defining roles, please enter the values in column B for your corresponding list of roles set up in Fusion Embed.
6	Ellipsis Icon	Gives further Custom Roles management options. Select Add an Application Role to add multiple Application Role Values for the same OGL Role. Select Delete Application Role to delete an Application Role Value. Select Delete OGL Role to delete an OGL Role along with all its Application Role Values.
7	Cancel	Discards any changes that were made and closes the interface. A confirmation dialog is displayed if there are unsaved changes. Select Cancel to close this confirmation dialog. OR Select Don't save to discard the changes and close the Custom Roles interface. OR Select Save & Exit to save the changes and exit the Custom Roles interface.
8	Save Roles	Saves the changes made to the field. The button only becomes active when an acceptable value is entered in the field.

Display Groups

Categorize and order the content in the Help Widget quickly and easily with the Display Group Manager.

Accessing the Interface

1. On the OGL Console homepage, go to the left navigation panel.

   You can see the Settings section in the navigation panel.

2. Select the Display Groups from the dropdown menu.

   

Understanding the Interface

Legend	Description	Additional information
1	Filters section	Filtering Content for Display Groups Use filters to locate items to associate with a display group. Select the Filters button to show or hide the filters and search box.
2	Close button	Use to close the Display Group Manager. A warning is displayed if there are unsaved changes.
3	Sort alphabetically	Use to sort items in alphabetical order (A→ Z). Note: Action cannot be undone.
4	Item name	Displays the item's name
5	Display group label	Displays the item's current display group association
6	Item status	Displays the item's status (i.e. Published)
7	Item count	Displays the total number of display items and the number of items per display group.
9	Display group name	Display group name field. Duplicate names are not allowed.
10	New display group button	Use the button to create new display groups.
11	Drag to reorder icon	Use the icon to manually reorder the items and/or display groups using drag and drop, or you can specify the order by numbering them. To reorder, drag and drop each display group/item in the order of choice.
12	Display group name	Displays the display group's current name.
13	Display group/ order number	Identifies the display group's order number. To reorder, edit the display group and specify the order by entering the required number in the number field.
14	Save all button	Saves all the changes made in the Display Group Manager.
15	Edit button	Use the Edit button to update the display group, this only includes the display group name, icon, and sequence numbering.
16	Toggle button	Use the button to toggle the display group as active or inactive. If set to inactive, the items associated with the display group will not be visible in the OGL Help Widget but can be accessed by using the search functionality in the OGL Help Widget. This functionality is helpful when you need to make items available only by searching in the OGL Help Widget.
17	Save button	Use to save changes made to the display group, this includes changes made to the name, icon, and sequence numbering.
18	Cancel button	Use to discard changes made to the display group, this includes changes made to the name, icon, and sequence numbering.
19	Delete button	Deletes the display group. A warning dialog box is displayed to confirm the action. This action cannot be undone. Items that were assigned to the deleted group will be assigned to the default display group. Note: You can close the Display Group Manager and to chose to not save the changes. This will discard the changes made and revert to the display groups prior to the delete action.

Creating Display Groups

When you create display groups in the Display Group Manager you provide a name and an icon, and then you can assign content.

To create a display group:

1. On the OGL Console homepage, go to the left navigation panel.

   You see the Settings section in the navigation panel.

2. Select the Display Groups dropdown menu.
   
3. Click New Display Group in the Display Group Manager
4. In the Display Group Manager window,
5. Enter the Name of the display group

   IMPORTANT: Your display group name cannot contain any special characters ( * | \ " : < > [ ] { } ` ( ) ' ; & $ )

6. Select Save
7. Add content to the display group by dragging & dropping to the display group
   
   
   
   
8. Select Save All to save the changes and close the Display Group Manager

Adding Content to Display Groups

You can add content by dragging the item from the right side and dropping the item into the appropriate display group on the left. After the item is added to a display group, the display group association tag is updated next to the item name. To remove items from a display group, simply drag and drop the item into the new display group. To see the contents of a display group, select the group's name on the left of the Display Group Manager.

Filtering Content for Display Groups

If you have many guides, you can use filtering or search for a guide to place in a display group. To access search and filters, select Filters at the top of the Display Group Manager.

Reordering Display Groups

Use the Display Group Manager to configure the order of display groups and the content within them. You can reorder display groups and guides using drag and drop, or you can specify order by numbering them.

To reorder display groups:

• Drag and drop each display group in the order that you want them to be displayed.
• Edit the display group  and specify the order by entering numbers in the display group order boxes.

  

To reorder guides:

• Specify guide order by selecting a display group then entering the numeric order of each guide in the order boxes.

  

Health

Developers can review guide issues from either the guide card for an individual guide or a list of all errors from the navigation panel.

If a guide has an error, for example if a smart tip has been incorrectly flagged as a sticky guide, this will show on the guide card as an error, as in the image below.

You can click on the icon to display the error.

Clicking on the error link shows details about the reported error and any recommendations to resolve it. You can now make the necessary change to the guide to resolve the issue if needed.

Alternatively, you can also see all guide health issues from the left navigation panel:

The Health modal will appear displaying a list of all guide errors identified within the Content library and any details about the errors.

The options available for the Health list are to either Hide or Dismiss the errors.

HIDE: Hides the error from the Health list and moves it to a list of hidden errors. You can use the "Show hidden items" checkbox to see all hidden items.

Note:

Selecting Hide has no impact on calculation logic and does not treat the error as 'resolved'.

Show hidden items: Toggles the Health list to show or hide all hidden errors.

UNHIDE: When "Show hidden items" is checked, any errors that are marked as hidden will be re-displayed in the Health list. Select Unhide to move the hidden error back to the Health list.

DISMISS: Removes the error from the Health list and marks it as resolved.

Note:

Dismissing a health error does not mean that the error has actually been resolved. You will still need to fix or repair the guide, as needed. Any errors that are dismissed will reappear within 24 hours in the Health list if OGL detects that the error still exists in the guide.

HIDE ALL: Hides all errors in the Health list and moves them to a list of hidden errors. Use "Show hidden items" to display all hidden errors.

Below is a list of the potential issues that you might find in Health:

Issue	Error	Description
Always Activation	ERROR_TYPE.WRONG_ACTIVATION	The launching conditions of this content are probably too generic. It is problematic because frequent checking the content in order to decide if it can be launched or not will add overhead and will result in slowing down Guided Learning. Please avoid displaying content with 'always' condition and narrow down the launching conditions (e.g. limit to certain pages if possible).
Content Type	ERROR_TYPE.PROBABLY_SMT	This content seems to be a smart tip or beacon but its type is different. Smart tips usually have a single step and they are pointing to a certain html element. They appear typically on hover event. Please change the type of this content appropriately.`
Sticky Guide	ERROR_TYPE.STICKY_FLAG_NOT_EXPECTED	Sticky flag is turned on a smart tip or beacon. This is usually not a correct setting because smart tips and beacons are used on a single page. Please turn off sticky flag.
Unpublished Launched	ERROR_TYPE.NOT_PUBLISHED_AND_LAUNCHED	This content is not published but it was launched somehow. Typically another content can trigger launching so you should search for dependencies. Please either publish this content or find the other one which triggers its launch.

Help Panel

Accessing the Help Widget Settings

1. Select the Content tab in the OGL Console

2. Select Help Widget Settings in the left panel
   
   
   
   

Modules

Accessing the Interface

1. Select the Content tab in the OGL Console
2. Select Modules in the left panel
   
   
   
   

Understanding the Interface

Legend	Name	Additional information
1	Search box	Provides dynamic search functionality.
2	Close	Closes the Fusion Modules interface. A warning will be displayed if there are unsaved changes.
3	New Item	Adds a new line to the list.
4	Name field	The name field cannot be empty. Duplicate values are not allowed.
5	Done/Save	Saves the changes made to the field. The button only becomes active when an acceptable value is entered in the field.
6	Delete	Deletes the line item. Action cannot be reversed and all linked content items will be disassociated.
7	Edit	Allows changes to be made to the field.
8	Cancel	Discards any changes that were made and closes the interface. A warning will be displayed if there are unsaved changes.
9	Apply	Saves the changes made. A confirmation is displayed if the operation has either been completed successfully or failed with errors.

Pages

A common method to determine when a guide should run or be visible in the Help Panel is to look at the page URL, or for Fusion, the page route. Getting the route in Fusion is not a straightforward task and keeping track of all the pages and their URLs or routes for an application can be a difficult task. In the Pages window, this is made simple for the user.

Configuring Pages

Various pages are automatically captured by OGL while creating OGL items. The page route is added to the list of pages in the Pages interface, some pages will be automatically named and some will remain undefined until an admin provides a name.

Legend	Name	Additional Information
1	Defined Pages tab	This tab lists all the pages with a defined name (i.e. Homepage)
2	Undefined Pages tab	This tab lists all the pages without a defined name, this means the page route has is known but OGL did not provide a name for the page. The name needs to be manually defined
3	Search box	Provides dynamic search functionality.
4	New Page	Use the button to define a new page in Page Manager. To define a page: Navigate to the page in Fusion (i.e Expenses page) Right-click on the page and select Inspect from the menu. Select the console tab Enter the following code iridize.master.getRoute(), then press Enter/Return Copy the returned page route Select New Page in the Page Manager Enter the copied route into the URL field (6) Define a name in the Name field, then select Save
5	Page name field (new page)	The name field cannot be empty. Duplicate values are not allowed.
6	Page URL field	Note this is the route automatically captured by OGL or returned by iridize.master.getRoute()
7	Delete	This action cannot be undone, and pages will need to be recaptured.
8	Save	Saves the changes made to the field. The button only becomes active when an acceptable value is entered in the field.
9	Page name field (existing page)	This name has been automatically defined by OGL
10	Page preview link	Provides a quick view of the captured page route. Th
11	Update button	This button is inactive by default and becomes active when updates are made in either the Name or URL field.

Using Pages Info for Activation Settings

From the OGL Console, select the check icon for the guide that you want to access.

By copying the route value for a page (highlighted in the image below), the developer can copy the URL (or route, in the case of Fusion) for use in configuring activation settings.

Once the URL has been copied, it is just a matter of pasting that value in the field outlined in red below. Be sure to paste in the value exactly as copied and do NOT enclose the pasted URL in brackets ( [ ] ).

Important: If a page has been defined in the pages Manager, then the condition can be added as a simple condition (When Page is (or is not)). When a page becomes defined in Page Manager, OGL will update the corresponding guides to reflect the page name.

For more information, refer to Enabling Guide Activation Settings.

Products

Accessing the Interface

1. Select the Content tab in the OGL Console

2. Select Products in the left panel
   
   

Understanding the Interface

Legend	Name	Additional information
1	Search box	Provides dynamic search functionality.
2	Close	Closes the Fusion Products interface. A warning will be displayed if there are unsaved changes.
3	New Item	Adds a new line to the list.
4	Name field	The name field cannot be empty. Duplicate values are not allowed.
5	Done/Save	Saves the changes made to the field. The button only becomes active when an acceptable value is entered in the field.
6	Delete	Deletes the line item. Action cannot be reversed and all linked content items will be disassociated.
7	Edit	Allows changes to be made to the field.
8	Cancel	Discards any changes that were made and closes the interface. A warning will be displayed if there are unsaved changes.
9	Apply	Saves the list of Fusion Products. A confirmation is displayed if the operation has either been completed successfully or failed with errors.

Theme

Oracle's Accessibility Program

Please note that modifying the Theme (Design Kit) might impact accessibility. For more information about Oracle's commitment to accessibility, see http://oracle.com/accessibility.

Accessing the Interface

1. On the OGL Console homepage, go to the left navigation panel.

   You can see the Settings section in the navigation panel.

2. Select the Settings dropdown menu.
3. Select Theme in the left panel.
   

Understanding the Interface

You can see two tabs, Theme Gallery and Upload/Download Theme.

Legend	Name	Additional Information
1	Theme Gallery	Theme Gallery tab opens.
2	Active Theme	The current theme which is active is displayed.
3	All Themes	Lists all the available themes.
4	Restore Default theme	Restores the theme selection to the default OGL theme.
5	Save	Saves the currently selected theme in the Theme Preview pane (7) as the theme for the account. WARNING: This action saves the selection for both development and production environments
6	Cancel	Closes the window,

Upload/Download Theme

Legend	Name	Additional Information
1	Upload/Download Theme	Upload/Download Theme tab opens.
2	Create New Theme	Create a new theme.
3	Upload your custom design	Upload a custom design kit to the account. Steps Description Choose a file Select the customized theme file saved in your local directory to upload to the Theme Gallery. Create a new theme Create a new custom theme using the OGL Theme Design Kit Update current theme Updates the Design Kit for the current (saved) theme selection. NA Tenancy - https://guidedlearning.oracle.com/account/theme/ EMEA Tenancy - https://guidedlearning-emea.oracle.com/account/theme/ Note: This will download as file iridize_design_kit.html file. Ensure you rename the file accordingly. Select theme after upload Automatically applies the newly selected theme to your application Publish current theme Publishes changes to the theme to Production Upload Uploads the selected
6	Restore Default theme	Restores the theme selection to the default OGL theme.
7	Cancel	Closes the window.

Configuring Themes

OGL includes several default themes. You can also customize tip colors, fonts, and tip positions as per your branding requirements.

Download the Design Kit

The Design Kit provides the ability to update the theme however you want, this article is meant to provide some basic guidelines and covers updating some of the basic attributes of the theme and does not cover advanced CSS methods.

1. Select the Content tab in the OGL Console
2. Select Theme in the left panel
   
   
   
   
3. Select the Download the Design Kit link
   
   
   
   
4. This will download as file iridize_design_kit.html file. Ensure you rename the file accordingly.
5. Save the HTML file to a local directory.

   Note: Rename the file accordingly, our recommendation is to rename it using the following convention: Design_Kit_ORGNAME_DD_MMM_YYYY

Update the Design Kit

To update the design kit, you will need to use a suitable text/HTML editor.

1. Open the Design Kit in a browser
2. Open the same file with the HTML/text editor
3. Find the CSS class and update the relevant attributes
4. Save the changes, then refresh the Design Kit in the browser to preview the changes before uploading them to the OGL Console

Upload the Design Kit

1. Select the Content tab in the OGL Console
2. Select Themein the left panel
3. Select Upload Theme

   Note: The below interface will show
   
   

4. Select Choose File (A), then select the file saved in your local directory.
5. Select Create new theme (B). Note: Select Update current theme if you are updating an existing custom theme
6. Check the Select new theme after upload check-box

Common CSS Rules in the Guided Learning Theme

This article lists the most common CSS rules which can be updated to change the Guided Learning theme to suit your brand identity. The below CSS rules should be updated/inserted in the design kit. Note: This serves as a guideline.

To update the colors of the Guided Learning tooltips, find the expected Hex codes, then replace them with your preferred codes:

Swatch	Find	Expected #	Replace with
	#1b3b3f	15	own
	#477b82	11	own

Note: Perform a Find & Replace to quickly update

Image Reference	CSS Rule
	/*to change the color of the widget*/ .ouc-widget { background-color: #ED6B1A; }
	/*change color when you hover over the widget*/ .ouc-widget__launch a:hover { background-color: #ED6B1A; }
	/*change the widget header background*/ .ou-panel__header {background-color: #ED6B1A;}
	/*change the color of the display group, item with focus*/ .ou-panel__navlist ul li input:checked + label, .ou-panel__navsearch input:checked + label, .ou-panel__navsearch.active label { background-color: #00AAFF;} .ou-panel__navlist ul li input:checked+.dg-nav, .ou-panel__navsearch.active label, .ou-panel__navsearch input:checked+label { background-color: #00AAFF; border: 1px solid #00AAFF; }
	/*to change the color of the display group icon on hover*/ .ou-panel__navlist ul li .dg-nav:hover {background-color: #eee;}
	/*change the color of the Step Guide buttons*/ .iridizeStepGuideCloserButton a {background-color: #00AAFF;}
	/*change the color of the Step Guide view border*/ .iridize-step-guide-frame {border-right: solid 5px #00AAFF;}
	/*change color of the task list header*/ .ou-panel__task__header {background-color: #00AAFF;}
	/*change color of the step guide icon*/ .uc-panel__item__step { color: #00AAFF;}
	/*change color of the step guide icon on hover*/ .uc-panel__item__step:hover { color: #00b5ff;}
	/*to change the smart tip to an i with a matching border find div.ir-marker in the theme and replace with the below*/ div.ir-marker { /*changing this will affect the color of the help icon*/ background-color: #FFFFFF; border: 2px solid #1b3b3f; border-radius:15px; font-weight: bolder; font-size: 14px;} /*to change the ? to an i find div.ir-marker:after and replace with the below*/ div.ir-marker:after{ content: 'i'; color: #1b3b3f;}
	/*change the background color*/ div.ir-marker { background-color: #12bc8d; } /*to change the ? to another letter, add the following CSS rule to the design kit if it doesn't already exist*/ div.ir-marker:after {content: 'i';} /*to change the ? to my own custom image, add the following CSS rule to the design kit if it doesn't already exist*/ div.ir-marker:after {content: none;} div.ir-marker { background: url(data:[your image goes here]) no-repeat left center; } /*You can use the following service to get the Data URI of your image - https://dopiaza.org/tools/datauri/index.php*/
	/*to change the color of the feedback dialog*/ .ir-feeback__footer__submit{background-color : #00AAFF;} .ir-feeback__footer__skip{background-color : #00AAFF;}

Custom CSS Rules for Guided Learning Theme

Enabling Multiple Styles in the same Guide

Guided learning allows for custom CSS classes where there is a requirement to have different formatting for tips or help icons within the same guide (or even the same step). An example of this would be having a different look for Smart Tip with varying levels of information, you could have red, amber, and green alerts with varying information.

All of your CSS styles must go between the IRIDIZE_CUSTOM_THEME_START and IRIDIZE_CUSTOM_THEME_END comment lines in the Design Kit. Examples are in the table below. You can set your own class names (i.e. ORG_CUSTOM1 instead of RED_ALERT).

Reference Image	CSS Rule
	Theme default, no custom CSS
	/*The following code will result in the help icon having a red background when the RED_ALERT class is active*/ div.RED_ALERT.ir-marker{background-color: red;}
	/*The following code will result in the help icon having an amber background when the AMBER_ALERT class is active*/ div.AMBER_ALERT.ir-marker{background-color: #F7AC08;}
	/*The following code will result in the help icon having a green background when the GREEN_ALERT class is active*/ div.GREEN_ALERT.ir-marker{background-color: #599964;}
	Theme default, no custom CSS
	/*The following code will result in the Next and Done buttons being RED when the RED_BTN class is active*/ div.sttip div.tooltip.RED_BTN div.stFooter [data-iridize-role="nextBt"] { background-color: red; }
	/*The following code will result in the Next and Done buttons being AMBER when the AMBER_BTN class is active*/ div.sttip div.tooltip.AMBER_BTN div.stFooter [data-iridize-role="nextBt"] { background-color: #F7AC08; }
	/*The following code will result in the Next and Done buttons being GREEN when the GREEN_BTN class is active*/ div.sttip div.tooltip.GREEN_BTN div.stFooter [data-iridize-role="nextBt"] { background-color: #599964; }
Grey image missing	/*The following code will result in the back button being grey when the GREY_BTN class is active*/ div.sttip div.tooltip.GREY_BTN div.stFooter [data-iridize-role="prevBt"] { background-color:grey; }
	/*The following code will result in the help icon having a red level indicator as 5 when the RED_ALERT class is active*/ div.RED_ALERT.ir-marker:after {content: "5";}
	/*The following code will result in the help icon having a the $ when the GREEN_ALERT class is active*/ div.GREEN_ALERT.ir-marker:after {content: "$";}

Once the updates have been made, upload the Design kit to Guided Learning (see Upload the Design Kit in Configuring Themes).

Set the Custom CSS Class for Tooltips

1. Open the item with the OGL Full Editor
2. Expand the Display Settings section in Step Settings
3. Find the Custom classes field and set the custom class for the tooltip

   Note: Set multiple custom classes by separating the class name with a single whitespace ( <custom_class_name_1><whitespace><custom_class_name_2><whitespace><custom_class_name_3>)
   
   

4. Save the changes and close the OGL Editor
5. Validate the changes in your test environment
   
   
   
   

Training Types

Defining Training Types will help you organize your content and more importantly help you understand which items are being accessed the most by users from OGL Analytics.

Accessing the Interface

1. Select the Content tab in the OGL Console

2. Select Training Types in the left panel
   
   

Understanding the Interface

Legend	Name	Additional Information
1	Search box	Provides dynamic search functionality.
2	New Item	Adds a new line to the list.
3	Name field	The name field cannot be empty. Duplicate values are not allowed.
4	Done/Save	Saves the changes made to the field. The button only becomes active when an acceptable value is entered in the field.
5	Edit	Allows changes to be made to the field.
6	Delete	Deletes the line item. Action cannot be reversed and all linked content items will be disassociated.
7	Cancel	Discards any changes that were made and closes the interface. A warning will be displayed if there are unsaved changes.
8	Apply	Saves the changes made. A confirmation is displayed if the operation has either been completed successfully or failed with errors.

Translation

Oracle Guided Learning is a global platform that caters to users from diverse linguistic backgrounds. It is designed to be inclusive and accessible, allowing you to customize your guides in multiple international languages. The following articles explain the process of translating guides and managing multi-language guide content. Translation of guides allows you to dynamically control which language of the guide will be displayed to the end user. Once the guides are exported you can translate the relevant text in the provided files and import them back to OGL with the new language. You can translate your guides manually using an external translation service or use OGL's new Automated Machine Translation feature. The Translation feature is available only to OGL Premium accounts.

Note:

For information about OGL Premium, visit: https://education.oracle.com/oracle-cloud-guided-learning-premium

Note:

• Please remember that with OGL, translations are only available from the generic language of English to other languages. It is not possible to use machine or automated translation to translate guides that were originally created in other languages, including US English.
• Please make sure to create all content in the designated folder Generic Language.
• The guides in the Generic Language folder are the main guides, and all the edits are done in the main guide, like:
  • Additional steps, adding a smart tip, removing a step.
  • When creating English guides, it is crucial to consider the possibility of them being translated into foreign languages in the future. For this reason, the tip width of each step should be adjusted accordingly.
  • Adding additional selectors for foreign languages.
  • Text updates are done in the respective languages using the OGL Content Editor.
• To ensure a successful translation with Machine Translation and Automated Translation, each step in a guide should not exceed 5000 characters, including HTML tags. If a step is longer than 5000 characters, the translation attempt will fail and result in an error.
• Guides must be published or unpublished in all the foreign languages it was translated into.
• If you deactivate a guide in the default OGL language folder, it will also be deactivated in the foreign languages folder, and vice versa.

Multi-Language Functionality

The Multi-Language functionality allows you to create copies of an OGL guide (i.e., process guide, smart tip, etc.) into additional languages. With this feature, the original guide and all translated versions of the guide will all share the same apiName. Once the guide has been duplicated, you can export the guide contents and properties into a ZIP file to be translated using an external translation service, such as Oracle's Go Portal. Once translated, you will be able to import the guide and properties back into your OGL content library to be deployed in their target languages for end users to consume.

Tip:

OGL's multi-language functionality supports supports over 290 languages.

Machine Translation

Once multi-language guides have been been created in the OGL console, you will need to manually translate the guides into the target languages using an external translation service. With the help of Oracle's Go Portal, this Machine Translation method enables you to manually translate guides and properties files into different languages. To use this method, you'll need to export your guides, generate a ZIP file of the guides, then upload it to Go Portal for translation. Once the translation is complete, you can download the file and re-upload it to OGL to deploy the guides in different languages.

Tip:

Machine Translation method supports 30 languages.

Automated Machine Translation

Beginning in 23C Release, OGL now offers Automated Machine Translation as an enhanced translation method. With this method, you can instantly translate guides into provided languages using AI machine translation directly from within the OGL console, without the need to export/import guides.

See the following subsections to learn more about how to translate your guides.

Multi-Language Functionality

Overview of Multi-Language Functionality

The Multi-Language functionality allows you to create copies of an OGL item (i.e., guide, smart tip, etc.) into additional languages (i.e., An English worded OGL item can be made available in Dutch, French, etc.).

Note:

Kindly note that this feature does not have an automatic translation capability for the guides.

Every account/AppID has a default language set (this will be English for our examples). The default language can be set to any OGL-supported language. In addition to the default language, you will need the multi-language JavaScript line of code added to the OGL JS. Please refer to the javascript in this article.

The screenshot of the OGL console below highlights the default language or the currently selected language if there are multiple options available in the account.

Important:

The Multi-Language functionality:

• Works on an item-by-item basis. Bulk actions are not possible.
• Does not apply to Training Content (Use the properties file to translate these item types. Refer to OGL Console Left Panel - Translation.
• Allows use of the Content Editor in the alternate language folder to perform quick manual translations without having to wait on/purchase a translation service.
• Updates (OGL item structure & settings ) are inherited. You only need to update the text in alternate language OGL item(s).
• Allows you to have different languages for different OGL items (i.e., OGL Item A can have languages EN(default), FR, DE, and OGL Item B can have languages EN(default), ES, NL).

Default Language Setting

Previously Oracle Guided Learning’s default language for guides was English. From OGL release 21A, we have the facility to set the default language to any Fusion-OGL-supported language.

Accessing and Using the Multi-Language Functionality

1. On the OGL console, go to Contents.
2. On the target guide, select the ellipsis icon () and then Languages ().
   

   The Languages modal window is displayed now.

   

   Language Search Field

   Use this field to search for a target language. Search results are filtered dynamically.

   Existing Languages in the Account/AppID

   Languages currently available in the account/appID are displayed in this section (at the top). A horizontal line acts as a divider between 2 and 3.

   OGL Supported Languages

   This section lists the OGL supported languages. You can select a language by clicking the green button (). The selected language will be listed in the Current Selected Languages section (5).

   Restriction:

   Although there might be an extensive number of languages listed in OGL, for Fusion only the languages listed below are supported.
   • Arabic
   • Chinese (Simplified)
   • Chinese (Traditional)
   • Czech
   • Danish
   • Dutch
   • English
   • Estonian
   • Finnish
   • French
   • French (Canadian)
   • German
   • Greek
   • Hebrew
   • Hungarian
   • Italian
   • Japanese
   • Korean
   • Latvian
   • Lithuanian
   • Norwegian
   • Polish
   • Portuguese (Brazilian)
   • Portuguese (European)
   • Romanian
   • Russian
   • Slovak
   • Spanish
   • Swedish
   • Turkish

   Current Selected Languages - Previously Created

   When an OGL item has an existing copy in alternate languages (i.e English) the languages are listed first as read-only.

   Current Selected Languages - To be added

   Current language selections are listed below the existing languages for the OGL item. To remove a language from the current selection, click the red button ().

   Apply and Save and Exit buttons

   Once you have made your selections, click on Apply, then Save & Exit to create alternate language copies of the OGL item.

3. Choose the language(s) to which the guide needs to be translated. You can select multiple guides at once.
   

4. Select Save & Exit.

   The guide is now cloned.

5. Navigate to the specific language folder to which you have translated the guide.
   

   The guide is now cloned with same API ID.

   

   Note:

   Kindly note that this feature does not have an automatic translation capability for the guides. Once you have cloned the guide, it will remain in the generic language, and you will need to utilize the Go Portal to translate the guide or purchase a translation service. Another option would be to manually translate the guide through a third-party translator such as Google Translate for a quick translation.

6. Contact your OGL Account Manager to purchase a translation service.

7. Alternatively, use a third-party translator such as Google Translate for a quick translation.
   1. Open the content editor of the guide that you want to translate.
      

   2. In a new browser tab, go to Google Translate.

   3. Copy the contents from the content editor and paste it into the Google Translator's input column.

   4. Select the desired output language, and the content is instantly translated.
      

   5. Copy the translated content from Google Translate and paste it back into the content editor of the guide.
      

   6. Select Apply and then Save & Exit to save the changes.

      Now the content is manually translated. You can also update the guide title manually to the desired language.

      

WARNING:

Deleting an OGL item from the alternate language folder will delete all copies of the OGL item. You can restore the OGL item by recovering it from the Archive folder.

Understanding the relationship between the default OGL item and its alternate language copies

The OGL items in the default language are the primary data files where critical information relating to the OGL items is stored. An OGL item in an alternate language cannot exist without an OGL item in the default language.

Legend:

= Independent

= Inherits settings/value from the Default Language OGL item

Information Stored	Default Language OGL item (i.e. English)	Alternate Language 1 OGL item (i.e. Dutch)	Alternate Language 2 OGL item (i.e. French)
Display Settings, Activation Settings, and Advanced Settings (incl. Selectors)
OGL item Name
OGL item Step Text
Number of Steps
Step Sequence
OGL item Status
apiName
OGL item Property: Products
OGL item Property: Modules
OGL item Property: Sticky Guide
OGL item Property: Managed Guide
OGL item Property: Labels
OGL item Property: OGL item Type
OGL item Property: Descriptions (Keywords)
OGL item Activation Conditions: Role
OGL item Activation Conditions: Time
OGL item Activation Conditions: URL (incl. Autosegmentation)
OGL item Activation Conditions: All other (assuming the condition can be localized)
Editing Steps in the Default Language for Multilingual OGL item: Adding a step		1	1
Editing Steps in the Default Language for Multilingual OGL item: Deleting a step		2	2
Editing Steps in the Default Language for Multilingual OGL item: Text change		3	3

Note:

1. Inherits the default language text(not auto-translated), needs to be updated using Content Editor in the relevant alternate language.
2. Deletes the step in all copies of the OGL item.
3. Text changes to existing steps are not auto-translated, needs to be updated Content Editor.

Important:

Creating a new OGL item in the default language does not automatically create the alternate language copies of the OGL item.

Machine Translation

With the help of Oracle's Go Portal, the Machine Translation method enables you to translate guides into 30 languages. See the list below for the languages supported.

• Arabic
• Chinese - Simplified
• Chinese - Traditional
• Croatian
• Czech
• Danish
• Dutch
• Finnish
• French - Canada
• French - France
• German
• Greek
• Hebrew
• Hungarian
• Italian
• Japanese
• Korean
• Norwegian
• Polish
• Portuguese - Brazil
• Portuguese - Portugal
• Romanian
• Russian
• Slovak
• Slovenian
• Spanish - Worldwide
• Swedish
• Thai
• Turkish
• Vietnamese

Translating the Guides Using Machine Translation

In the Machine Translation method, you'll need to generate a ZIP file of the guides, then upload it to Go Portal for translation. Once the translation is complete, you can download the file and re-upload it to OGL to access the guides in different languages.

Note:

• You can use machine translation up to four times a year without any cost. Any further translations will be charged.
• The turnaround time is 24-48 hours.
• The best practice is to have the content ready and signed off in the Generic Language (English) before submitting the machine translation.
• Guides will only be tested in the default language. The client is responsible for testing the foreign-translated content (only for Managed Service clients).

This section will guide you on how to translate your guides using machine translation.

Important:

To use Machine Translation, you need:

• Java Runtime Environment installed on your PC.
• Drop Generator installed on your PC.
• Go Portal access.

To translate:

Step 1: Export the OGL content from the Generic Language folder (English folder).

Note:

By default, OGL guides are in English. If you're using an APP ID without translated guides, you will only have a generic folder including all the English guides. As soon as a translation is completed, folders with the translated content in other languages will be created.

1. On the OGL homepage, select Settings > Translations.
   

   The Translations modal window is displayed now.

   1. Select Export.
      

      A ZIP file containing your guides is sent to your email Id.

      

   2. Go to your email inbox and select Download.
      

      The browser now downloads the ZIP file.

   3. Navigate to your Downloads folder in the local drive and unzip/extract the downloaded file.
      

      After extracting the folder, you will notice three subfolders named Active, Testing, and Import and a README.html file.

      

      Note:

      Active:

      This folder contains the guides with status as published in the OGL dashboard from different languages/ default languages.

      Testing:

      This folder contains the guides with status as a draft in the OGL dashboard from different languages/ default languages.

      Import:

      This folder is used to import the translated content to the OGL dashboard in different languages.

      Readme:

      This is an HTML file that gives insights into export and import.

Step 2: Send the extracted files to Go Portal for translation.

Note:

Please note that Go Portal accepts only ZIP files created using the Drop Generator. The Drop Generator is a utility used for creating evaluation/translation drops from source files that you have available locally.

1. Navigate to the "testing" folder within the extracted folders.
   

2. Go to the subfolder named "--".

   Note:

   “--” is the default name for generic folders.

   You can see the list of existing guides in the English language, identified by their API IDs.

   

3. Select the guides you want to translate, copy and paste them to a new folder.

   Tip:

   • Use the API names of the guides to identify the exact guides you want to translate.
   • Consider renaming the new folder to make it easier to identify.
   

4. Copy and paste the application PROPERTIES File (.properties) from the testing folder to the newly created folder.The application PROPERTIES File contains all the basic setups like Next, Back, Done, Help, etc.
   

5. Use the Drop Generator to compress the files.

   Note:

   If the Drop Generator is not installed on your computer, you can download it from IPS Shopfront. Alternatively, select here to start the download process.

   

   Note:

   To open the dropgenerator-gui.jar file on your PC, you must install the Java Runtime Environment.
   1. Open the Drop Generator.

      The below interface is displayed.

      

   2. Generate the ZIP file using the Drop Generator. Follow the below steps:
      1. Select Scan files.
         

      2. Navigate to the directory where translation request files are stored.
         

      3. Choose Drop type as UI and Scan type as Directory.
         

      4. Select Ok.

      5. After scanning, the files are displayed as shown below.
         

         Make sure there are no warnings or errors in the Issues tab.

         

      6. Select Generate Drop.
         

      7. Fill in the parameters as follows:
         • Product = iridize (all lowercase).
         • Version = 2.0.
         • Drop nr = 10 (Default value),20, 30.

         • Group = iridize (All lowercase).

           Note:

           The above values are predefined. They have to be maintained for all the drops.
           

      8. Select OK.
         

         The ZIP file is now generated.

         

   3. Navigate to the Go Portal.
      1. Login to the Go Portal using your organization's SSO credentials.

         After logging in, the below interface is displayed.

         

      2. Select the project Oracle guided Learning for Fusion Applications from My Projects.

         Note:

         Only projects that you own are accessible to you.
         

      3. For automatic translation:
         1. Select New QA Drop.

            Note:

            You must be a project owner to create a drop.
            

         2. From the dropdown, select New Resource Generation by uploading file.
            

         3. Upload and submit your file.
            • Select your file.
            • Add a friendly title.
            • Component: Select iridize
            • Submit drop for: UI
            • Select file: Choose the ZIP file created via Drop Generator.
            • Select Submit.
            

         4. After submitting the file, select the Refresh button in the top right corner to view the translation progress.
            

            Note:

            Once the translation process is complete, the status of the uploaded drop will change to Finished.

            

         5. Select the Drop Container you named according to the Project or Customer.
            

         6. Select the Component link - iridize.
            

         7. Go to the Artifacts tab.
            

         8. Select the language links corresponding to your desired language to download the translated content.
            

      4. For manual translation:
         1. Select New Translation Drop.
            

         2. Select OK. The latest feature New Resource Generation by uploading file is supported.
            

         3. Add Basic Information.
            • Enter a friendly title.
            • Enter a meaningful drop number or accept the default.
            • Add drop description if required.
            

            Select Next.

         4. Choose UI only and select Next.
            

         5. Choose the Components and select Next.
            

         6. Add the languages that you would like to translate and select Next.
            

            Note:

            Currently, we support 29 languages for manual translation. If you require a language that is not listed, kindly email [e-mail], and we will add it as requested.
         7. Set the translation frequency and select Next.
            

         8. Review the summary and select the Create button.
            

         9. After submitting the file, select the Refresh button in the top right corner to view the translation progress.
            

            Note:

            Once the translation process is complete, the status of the uploaded drop will change to Finished.

            

         10. Select the Drop Container you named according to the Project or Customer.
             

         11. Select the Component link - iridize.
             

         12. Go to the Artifacts tab.
             

         13. Select the language links corresponding to your desired language to download the translated content.

             Note:

             • Download one language at a time,
             • This will download a zip file.
             

Step 3: Import the translated guides to OGL.

1. Open the downloaded machine translated Zip file & keep it ready for copying.

   (In the following example, we have retrieved the translated content in Czech.)

   

2. Navigate to the folder where you first downloaded the ZIP file from the OGL Dashboard.
   

3. Open the import folder and create a new folder. Name the folder with the language code for which you translated.

   Tip:

   To import French guides, the folder should be named "fr," while for Czech, it should be named "cz," and so on.
   

4. Copy and paste the translated content to the specific language folder.
   

5. Compress/Zip the import folder alone.
   

6. Navigate to the OGL dashboard.

7. Go to Settings > Translations.
   

   The Translations modal window is displayed now.

8. Under the Import section, select Choose a file andchoose the file named"import.ZIP".
   

9. Set the encoding to utf-8-sig.
   

10. Check in the Connected checkbox.

    (If this option is not checked, any additional modification cannot be made in the guide.)

    

11. Select the Import button.
    

    The translated content is now imported.

12. Verify all the translated guides are available in the respective language folders.
    1. On the OGL console, select Contents.
    2. Select the GENERIC LANGUAGE dropdown and choose the desired language.
       

       The translated guides are now displayed.

       

    3. Launch any guide in the Fusion Application by changing the language in the Application login screen.

       (Normally, the guide will progress similarly to the default language guide. If the translation guide does not progress like the default language guide, follow the steps in the troubleshooting tips.)

Automated Machine Translation

Improving upon OGL’s existing multi-language support capabilities, this new functionality now instantly translates guides into provided languages using machine translation directly from within the OGL console, without the need to export/import guides. This feature is available only to OGL Premium accounts.

Note:

For information about OGL Premium, visit: https://education.oracle.com/oracle-cloud-guided-learning-premium

This initial release of the Automated Machine Translation feature is being introduced in an early developmental stage with the intent to provide you with early access to this emerging functionality. The following are known limitations of this feature in 23C release:

• Not all languages are supported at this time. Future enhancements are planned to improve upon this feature’s capabilities, performance, and expand the library of available languages.
• This feature will only translate guide contents, not application properties or selectors.
• Each translation is subject to a character limit of 5,000 characters per step (including HTML tags).
• If the selected Generic Language is not on the list of available languages as listed in the Translation dialog box, the translation will fail and return an unspecified error message.

Note:

This feature requires the following OGL security role and permissions: Owner role → Change Application Settings permissions

Translating Individual Guides

1. From the My Content page, select the “More…” icon in the lower right corner of the guide you wish to translate.
   

2. Select Translate from the actions menu.
   

3. The Translation modal opens.
   

4. Select the “+” button next to the language(s) you wish to translate the guide from the list of available languages on the left. Any selected languages will appear in the Target Languages, then select Save and Exit when done.
   

5. A confirmation dialog box will appear (read carefully) and will prompt you to confirm the action.
   

6. Once the translation is complete, a confirmation message will appear at the top of the Translation modal to confirm that the guide has been translated.
   

   Note:

   Translations cannot be undone. To restore the guide to a previous version, use the Version History in the Guide Status.

7. The translated guides will now appear in their respective language folders in the My Content page. To toggle between each language folder, select the language dropdown menu.
   
   

8. If you make any content changes to the original guide and then translate the guide again, you will be prompted with an option to retranslate the guide for all target languages.
   

Translating Multiple Guides (Bulk Action)

1. From the My Content page, select one or more guides that you wish to translate, then select Translate from the Bulk Actions dropdown menu.
   

2. The Translation modal opens.
   

   Note:

   With bulk translations, any pre-existing translated languages will not be displayed in the Target Languages column. Any translations applied using Bulk Actions will affect all selected guides and will overwrite any existing translations. To translate specific guides into specific languages, consider translating the guide(s) individually.

3. Select the “+” button next to the language(s) you wish to translate the guide from the list of available languages on the left. Any selected languages will appear in the Target Languages, then select Save and Exit when done.
   

4. Once the translation is complete, a confirmation message will appear at the top of the Translation modal indicating that the job has been scheduled and that an email will be sent to notify you when completed.
   

5. Check your email inbox for a message from Oracle Guided Learning <[e-mail]>. The message should look like this:
   

6. Open the attached Excel spreadsheet to view the translation status of all selected guides.
   

7. The translated guides will now appear in their respective language folders in the My Content page. To toggle between each language folder, select the language dropdown menu.
   
   

Using the Multi Language Widget

A user may choose to select an alternative language available on the OGL widget. Here is an easy way to do this:

1. Open the Guided Learning widget.
   

2. At the bottom-left of the open widget, click the Language Selection icon () then select the desired language from the menu.
   

All guides available in the selected language will now display in the widget. For example, if you selected Dutch from the available languages, all Dutch guides will now display in the widget.

Once you sign out of the Fusion application and sign back in, the widget language will default to the language you have previously chosen.

Note:

If a user does not manually select a language from the OGL Language Menu, OGL defaults to the Fusion application language for the session.

User Management

Once your OGL account is created, you can add new users with different permission levels. The new users can create, publish, delete guides, edit content, view analytics, etc. We recommend you follow the Least Privilege principle when granting permissions to new OGL users, especially the permission to publish guides.

You can set up multiple types of users depending on the level of access you want each user to have. Each user is identified by their name, email address, and the permissions assigned to them.

Introduction to OGL Roles

Before you set up users in OGL, you should understand the roles and permissions that you can assign to a user.

Note:

The roles discussed below only apply to the OGL Console and are not related to the application roles.

Roles & Permissions

Viewer: Executive sponsors are the common target audience for this role which only requires the ability to see what guides exist and view the Analytics Dashboard.

Permission	Detail
Preview a guide	Preview Guides
View Analytics	View Analytics

Editor: The Editor role addresses users who only need to work with the copy/text in the guides and messages to end-users. This allows writers to be able to get into the system and provide content without exposing them to publishing and other mission-critical capabilities.

Permission	Detail
Access Content Editor	Edit OGL item text via Content Editor
Manage Messages	Create, Update, Clone, and Delete Messages

Developer: This role enables admins who should be working with the detailed features within individual guides, while not opening up system-wide settings that would affect all Editors and Developers.

Permission	Detail
Edit Guides	Update OGL item name(s) View Guide in Full Editor Edit Guide, Video, Links, Tasks Lists via Full Editor Edit Settings for Guide, Video, Links, Tasks Lists in Dashboard Edit Activation Settings for Guide, Video, Links, Tasks Lists in Dashboard
Create Guides	Create/clone OGL item(s)
Delete Guides	Delete/recover OGL item(s)
Publish Guides	Activate/inactivate OGL item(s) Publish/unpublish OGL item(s) Publish unpublished revisions of OGL item(s)
Edit Managed Guides	Edit OGL items classified as managed by Oracle University

Owner: Within each organization, there should only be 2-3 people with this level of access. The permissions included in this role enable the admin to make changes to the system that will affect every user and guide therein.

Permission	Detail
Manage Users	Add/delete users from the appID Assign/revoke user permissions
Manage Help Widget Settings	Update the help widget sort order Update the OGL Widget settings for development and production
Manage Display Groups	Create, update, and delete display group(s)
Manage Roles	Create, update, and delete simplified role(s)
Manage Pages	Create, update, and delete OGL pages for use in conditioning content in the library
Manage Products & Modules	Create, update, and delete OGL Products and Modules which are used in OGL analytics and as content filters
Manage Training Types	Create, update, and delete training type(s)
Manage Themes	Can update the theme to any of the available themes in the OGL Console. Can download the available Design Kit(s) in the appID Can update the theme via the appID's Design Kit Can upload modified Design Kit(s) to the appID
Change application settings	Enable feedback Manage feedback settings for development and production Update the application(sub-account) name
Create Managed Guides	Set a guide as a managed guide
Manage Comments	Manage comments in the full editor
Reset end-user usage data	Reset user analytics data
Manage Cloud Configuration	Manage Cloud Configuration in the OGL Console
Manage Oracle Content	Manage Oracle Content in the OGL Console.
Batch Update Guides	This feature enables you to update guides in batches.

Assigning Roles and Permissions

You can assign all of the permissions within a role to a user, or assign specific permissions. Depending on your approach, the role icons will change so you can quickly see which roles and permissions a user has:

= ALL of the permissions within the OGL role are assigned to the user.

= SOME of the permissions within the OGL role are assigned to the user.

= NONE of the permissions within the OGL role are assigned to the user.

• To revoke all user permissions for a particular OGL role simply click on or to make it
• To assign all user permissions for a particular OGL role simply click on to make it
• To assign some user permissions for a particular OGL role simply click on , then proceed to assign/revoke the required permissions

Adding Users

Note:

Only the identified client-side OGL Admins have the access to add additional users to the account.

Use the user's email address to add them to the OGL.

To add users:

1. On your OGL console's navigation menu, select Settings > User Management.
   

   The User Management modal window appears.

2. Select the Add Users button.
   
3. Enter the new user's email address in the Email field, assign the user permissions, then select Save..
   

   Note:

   See theabove "Assigning Roles and Permissions" section to learn more.
4. Select Close (X) to exit the User Management modal window.

Removing Users

To remove Users:

1. Navigate to the User Management modal window.
2. Check in the checkbox at the beginning of the line that lists the user you want to remove. Once checked in, the Delete button appears.
   
3. Select the Delete button.

   The user is now removed from OGL.

Exporting the OGL User Matrix

You can export the OGL user matrix in ".xlsx" format with a single click/selection.

1. Navigate to the User Management modal window.
2. Select the Export button () to download the user matrix.
   

   The browser now downloads the .xlsx file.