This article applies to Quebec, Rome and San Diego instances.
As part of the San Diego GA, we are releasing a new language “Portuguese” (pt), which will be available in the language dropdown when creating a NLU model for VA (see NLU language support). This will be in addition to the existing “Brazilian Portuguese” language supported. With this new language release, we are recommending customers to use “Portuguese” over “Brazilian Portuguese” for the following reasons:
- Portuguese will be able to cover “Brazilian Portuguese” locale as well.
- Portuguese intent prediction quality will be significantly better than the current prediction quality of Brazilian Portuguese available in San Diego
- Portuguese language will also support “Vocabulary Sources”, which will improve intent predictions and make it easy to point to list of values in table/static list to promote better language understanding
- Portuguese model training will be “fast training” and the training response will be in a few minutes compared to the current asynchronous training for Brazilian Portuguese which can take anywhere from 15 minutes to a few hours.
The recommendation for customers currently using Brazilian Portuguese is to port the model content to Portuguese and retrain the model. Customers can export the “bp”/Brazilian Portuguese existing model to CSV through the new export-import feature introduced in San Diego and import it back as a “pt”/Portuguese model (see Create NLU model from CSV and Export NLU model).
Please note that starting Tokyo, Brazilian Portuguese Servicenow NLU model prediction performance will be on par with that of Portuguese models and so customers can continue to use which ever language they need
Using Portuguese Servicenow NLU Models instead of Brazilian Portuguese models on Rome/ Quebec instances:
If the customer is on Rome/Quebec, they can still make use of this language by pointing their instance to the latest version of NLU Service (SanDiego.0). Please follow the below steps for that,
1. Set system property glide.mlpredictor.option.nlu.authoringModel.version.override to {'language.ModelName': 'pt', 'version.ModelName': 'sandiego.0'}, where ModelName is the NLU model name from sys_nlu_model table. If there are multiple language models, update the system property like this:
{
"language.ModelA": "pt",
"version.ModelA": "sandiego.0",
"language.ModelB": "pt",
"version.ModelB": "sandiego.0"
}
2. To make sure you can use Portuguese in VA designer, you will need to do a couple of things (this is a workaround and is not officially supported in Rome/Quebec):
- Install Portuguese language on the instance. Activate “Portuguese” language in VA language settings screen
- Confirm there is an entry for Portuguese when you navigate to “sys_cs_nlu_language.list”
3. You can now map topics to the pt Servicenow NLU model and test it out in Topic Discovery.
Please note that the above approach assumes end users interact with VA using Portuguese instead of Brazilian Portuguese. That is, their session language is in Portuguese.
