Installing Language I/O Incidents in OSC BUI
The purpose of this article is to guide Oracle Service Cloud administrators through the installation and configuration of the Language I/O extension for Incidents translation in the Oracle BUI (Browser User Interface).
In this article:
- Installing the Language I/O Extension Zip
- Assigning Profiles
- Creating a Language I/O Status Custom Field
- (Optional) Creating a Custom Language Field
- Importing and Deploying the Language I/O Custom Object
- Adding the Extension to Incident Workspaces
- Setting the Server Configuration Settings
- Downloads
Installing the Language I/O Extension Zip
- Download the "LanguageIO_BUI_Incident.zip" file attached at the bottom of this article.
- Go to Configuration > Site Configuration > Add-In Manager.
- In the Ribbon, click New and select Agent Browser UI Extension.
- Open the ZIP file that you downloaded in Step 1:
- In the Ribbon, go to Details:
- Enter the following:
- Name: LanguageIO_BUI_Incident
-
Extension Type: Workspace
- Check the following settings in the Extension Files area:
- Set
configs.json
as the Configuration file - Set
init.html
as the Init file
- Set
- Click Save. The LanguageIO_BUI_Incident add-in is now visible in the Agent Browser UI Extensions tree:
Assigning Profiles
Assigning profiles is the way you configure the add-in so that only certain users, or user categories, can use it. To assign profiles, follow these steps:
- Select the LanguageIO_BUI_Incident extension the tree (see Step 8 screenshot above).
- In the Ribbon, click Profile Access and enable the extension for:
- all admins who will be editing extension configurations or workspaces, and
- all profiles that will use the extension:
- In the Ribbon, click Save & Close:
Creating a Language I/O Status Custom Field
This field stores the status of the most recent translation attempt.
- Go to Configuration > Database > Custom Fields.
- Create a new folder called Language I/O:
- In the Ribbon, click New to create a new Custom Field:
- Enter the following settings:
- Name: Language I/O Status
- Data Type: Text Field
- Column Name: in_status
- Size of Field: 64
- Set the visibility of the Custom Field to agents only. To do so, make sure that the Edit and Display boxes are checked in the Admin column boxes, and unchecked in the End-User column:
- Click Save, then click Yes to save your changes:
(Optional) Creating a Custom Language Field
- Go to Configuration > Database > Custom Fields.
- Select the Language I/O folder under Incident and click New to create a new field:
- Enter the following settings:
Name: Custom Language
Data Type: Menu
Column Name: linguistnow_locale
The name you choose (In this example, "Custom Language") is visible to the agents, and can also be set to be visible to end-users (see Step 5 below). Remember this name: you need it to set the server configuration properties (see Chapter 7). - In Data Details:
- Add a Menu Item for every language that you want to support:
Note: If you get an error message, click OK then refresh the page. - Hover your mouse over each language and write down their ID:
- Language I/O will request the list of all languages & their numeric IDs.
- You need the Language IDs to set the server configuration properties (see Chapter 7).
- Add a Menu Item for every language that you want to support:
- (Optional) Under Interface Visibility, you can make the Custom Language values that you set in Step 3 visible to end-users by checking the boxes highlighted in the following screenshot. If you do this, end users see a drop-down with each option in the customer portal. This allows them to select their preferred language themselves.
Importing and Deploying the Language I/O Custom Object
LNThread
custom object. This object holds translation information.- Download the "LNThread.zip" file attached at the bottom of this article.
- Go to Configuration > Database > Object Designer
- If you do not see the Object Designer option in the Database menu, add it as follows:
- Click the gear icon in the Configuration menu to customize the menu list:
- Search for Object Designer. Add it to your Database menu:
- If you do not see the Object Designer option in the Database menu, add it as follows:
- In the Ribbon, click Import. Import the .zip file. Answer "Next" to all prompts.
- Click Save.
Note: If you get an error message, click OK. - In the ribbon, click Deploy and check Deploy Immediately:
Depending on site usage, the installation may take between a couple minutes to a day. You can continue to work on the installation while this occurs, but you cannot use the Language IO extension cannot be used until the custom objects are deployed.
Check your inbox for an email like the one shown below that lets you know when the deployment is complete:
If you get the following errors, exit the and start the import process again.
After the objects have been deployed
- Click on Extra Options.
- Enable all LNThread permissions for any agents who will use the extension.
- Click Save.
Adding the Extension to Incident Workspaces
- First, log out of the Oracle Service Cloud Desktop application, then log back in.
- Go to Configuration > Application Appearance > Workspaces / Workflows
Open the desired workspace to edit it.
Add the Required Fields and Custom Fields
- Create a new tab.
- Make sure to check first that a Language I/O tab does not already exist.
- In the Ribbon, go to the Design tab and click Add Tab
- Move the tab to the desired position:
- Rename the tab to Language I/O.
- In the Ribbon, go to the Home tab and click the Text field:
- If you want to to create two fields side by side, create a table first to house these fields:
- In the Ribbon select the Insert Field tab.
- Drag the Custom Language field, then the Language I/O Status field into the top row of the Language IO tab:
Add the Extension
- In the Ribbon, select the Insert Control tab.
- Drag the "LanguageIO_BUI_Incident" extension from the "Agent Browser UI Extensions" group into the "Language I/O" tab.
- Select the LanguageIO_BUI_Incident extension within the tab
- In the Ribbon, go to the Design tab.
- Click Table Cell and select Increase Column Span.
- Click Position and select Fill Cell
- Click Size and set the Height to 700.
You might see an error. This is due to a bug in Oracle.
Add the Workspace Rule
- In the Ribbon, select Home, then click Rules
- Click Add Rule and create a rule with the following settings:
- In the Triggers tab:
- Click Add next to the A named event fires rule
- Click named event -> enter switch_to_messages_tab in the pop-up
- Click OK to save the rule name
- In the Then Actions tab:
- Click Add next to the Focus a Tab rule.
- Click Tab.
- Select the Messages tab set.
- Click OK to save the rule.
- In the Properties tab:
- In the Rule Name field, enter a name for the rule, for example "Language I/O - Switch to Messages Tab".
- Click Finish, then OK
- Click Save & Close to save and close the workspace.
- In the Triggers tab:
Setting the Server Configuration Settings
- Go to Configuration > Site Configuration > Add-In Manager > Agent Browser UI Extensions > LanguageIO_BUI_Incident > Profile Access:
- Set the appropriate values for each relevant profile:
- agentLanguage is the numeric ID of the language that agents will use. The default is 1, which represents English for default Language field users. For custom language field users, use the ID for the language agents that you defined earlier.
- languageField is the name of the field Language I/O will use to determine agent and customer languages. The default pulls from Oracle's Language field. For custom language field users, enter the Name value that you defined earlier.
- languageioLogin - Your Language I/O Customer Success Manager will give you the value for this field.
-
languageioUrl is the address of the Language I/O translation server. The default is
https://golinguist.com
. Your Language I/O Customer Success Manager will let you know if you should change this value. - qualityRatingType: If set to 0 no quality rating flags appear for translated messages. If set to 1 then a quality rating flag will appear next to translated customer messages
- wordcountThreshold: defaults to 0, if this is set to a number greater than 0 there will be an alert verifying if the agent wants to continue when an incoming message translation has a wordcount greater than the provided value
This example shows an installation that uses custom language fields.
If you want all profiles to use the same configuration, you can set the values for one and the profiles the apply it to all. To do this, set the necessary values, then:
- Click Save (Not "Save & Close").
- Click Apply and select Apply this configuration to all profiles and interfaces.
This applies the configuration that you set for the current profile and interface to all profiles and interfaces that are currently enabled.
Comments
0 comments
Please sign in to leave a comment.