Upgrading Language IO Incidents in OSC BUI

Update the Language IO Extension ZIP file 

1. Download the "LanguageIO_BUI_Incident.zip" file attached at the bottom of this article.
2. Go to Site Configuration > Add-In Manager > Agent Browser UI Extensions and select (single-click) the "LanguageIO_BUI_Incident.zip" extension.
3. Click Update in the Ribbon:
   
4. From the file explorer, select the "LanguageIO_BUI_Incident.zip" that tour downloaded in Step 1.
   • Make sure that you check the “init.html” and “configs.json” files in the “Init File” and “Configuration” columns (respectively)
5. Click Save in the Ribbon.

Verify Language IO Custom Fields

1. Verify the Status Custom Field
   • Since your are updating an existing installation, the Language IO Status Custom Field should already exist.
2. Verify the Custom Language Field
   • The Custom Language Field should already exist if your are updating an existing installation AND if you are using custom locales instead of the built-in interface locales.

Import and Deploy the Language IO Custom Object

1. Download the "LNThread.zip" file attached at the bottom of this article.
2. Go to Configuration > Database > Object Designer
3. Click Import on the Ribbon and import the .zip file:
   
4. Answer Next to the prompts to merge the object.
5. Click Save in the Ribbon.
6. Click Deploy in the Ribbon and check the Deploy Immediately box.
7. After you deploy the objects, click on Extra Options.
8. Enable all LNThread permissions for any agents who will use the extension.
9. Click Save.

Add the Required Fields and Custom Fields

1. Since your are updating an existing installation, the design tab for Language IO should already exist.
2. Make sure that the LanguageIO_BUI_Incident extension is still present on your BUI Incident workspace(s).

Verify Server Configuration Settings

1. Go to Configuration > Site Configuration > Add-In Manager > Agent Browser UI Extensions > LanguageIO_BUI_Incident > Profile Access and select the relevant profile and interface. Verify that the properties still have their respective values.
2. You can see two new settings:
   • Translation_QualityRatingType setting: Indicates whether or not agents are allowed to provide quality rating feedback on translated messages they receive from the end-user. Set to 1 to enable a flag rating mechanism, or 0 to disable.
   • WordCountWarningThreshold: defaults to 0. If this is set to a number greater than 0, an alert triggers to verify if the agent wants to continue when an incoming message translation has a wordcount greater than the provided value.

Downloads