Release Notes - Language I/O Incidents in OSC Desktop v3.0 (Q2 2023)
These are the Release Notes for version 3.0.
New
Introducing Translation Quality Rating flag for agents
An agent who receives a poor translation can now flag the translation accordingly. This feedback allows Language I/O to assess continued translation quality.
To enable this feature, assign the value 1
to the Translation_QualityRatingType
server configuration property in your settings.
This feature also stores the translation quality ratings in the OSC database and loads in the UI when you re-open a previously flagged incident.
Improvements
Improved settings for customers with multiple OSC sites
The new configuration setting Site_IncidentLocaleField_UseLabels
that allows customer to use the labels from their custom locale field (defined in Site_IncidentLocaleField
), rather than IDs.
This is useful for customers who want to use the same OSC consumer across multiple OSC sites, where the menu IDs are not the same.
Improved Language auto-detection functionality
Language auto-detection functionality now sets the detected language on the Incident server-side and client-side to prevent sync issues. This applies when using the standard OSC Incident Language field as well as when using a custom locale menu field.
The ln_status
custom field value is also set on the Incident server-side and client-side now to prevent sync issues.
Logging the version number at login
OSC now logs the version number of the Language I/O plugin in the initialization logs when agents log in, instead of when they open a workspace.
Comments
0 comments
Article is closed for comments.