はじめに
対話型AIプラットフォーム
チャットボットの概要
自然言語処理(NLP)
ボットの概念と用語
クイックスタートガイド
プラットフォームへのアクセス
ボットビルダーの操作
リリースノート
最新バージョン(英語)
以前のバージョン(英語)
廃止機能(英語)
コンセプト
設計
ストーリーボード
ダイアログタスク
ダイアログタスクとは
ダイアログビルダー
ノードタイプ
インテントノード
ダイアログノード
エンティティノード
フォームノード
確認ノード
ロジックノード
ボットアクションノード
サービスノード
Webhookノード
スクリプトノード
グループノード
エージェント転送ノード
ユーザープロンプト
音声通話プロパティ
イベント ハンドラー
ナレッジグラフ
ナレッジグラフの抽出
ナレッジグラフの構築
ボットにナレッジグラフを追加
グラフの作成
ナレッジグラフの構築
既存のソースからFAQを構築
特性、同義語、停止用語
変数ネームスペースの管理
更新
ノード間の質問と回答の移動
用語の編集と削除
質問と応答の編集
ナレッジグラフの分析
通知タスク
スモールトーク
デジタルスキル
デジタルフォーム
デジタルビュー
デジタルビューとは
パネル
ウィジェット
トレーニング
トレーニングとは
機械学習
機械学習とは
モデル検証
ファンダメンタルミーニング
ナレッジグラフ
示唆
ランキングおよび解決
NLPの詳細設定
NLPのガイドライン
インテリジェンス
インテリジェンスとは
コンテキスト
コンテキストインテント
割り込み
複数インテントの検出
エンティティの変更
デフォルトの会話
センチメント管理
トーン分析
テストとデバッグ
ボットと会話
発話テスト
バッチテスト
会話テスト
デプロイ
チャネル
公開
分析
ボットの分析
NLPメトリクス
会話フロー
Usage Metrics
封じ込め測定
カスタムダッシュボード
カスタムダッシュボードとは
メタタグ
カスタムダッシュボードとウィジェット
ユニバーサルボット
ユニバーサルボットとは
ユニバーサルボットの定義
ユニバーサルボットの作成
ユニバーサルボットのトレーニング
ユニバーサルボットのカスタマイズ
他言語の有効化
ストア
プラントと使用
Overview
Usage Plans
Support Plans
Invoices
管理
ボット認証
複数言語対応ボット
個人を特定できる情報の編集
ボット変数の使用
IVRのシステム連携
一般設定
ボット管理
ハウツー
会話スキルの設計
バンキングボットを作成
バンキングボット – 資金の振り替え
バンキングボット – 残高を更新
ナレッジグラフを構築
スマートアラートの予約方法
デジタルスキルの設計
デジタルフォームの設定方法
デジタルビューの設定方法
データテーブルのデータの追加方法
データテーブルのデータの更新方法
Add Data from Digital Forms
ボットのトレーニング
示唆の使用方法
インテントとエンティティのパターンの使用方法
コンテキスト切り替えの管理方法
ボットのデプロイ
エージェント転送の設定方法
ボット関数の使用方法
コンテンツ変数の使用方法
グローバル変数の使用方法
Web SDK Tutorial(英語)
Widget SDK Tutorial(英語)
ボットの分析
カスタムダッシュボードの作成方法
カスタムタグを使ってフィルタリング
管理
ボット管理者コンソール
ダッシュボード
ユーザーの管理
ユーザーの管理
グループの管理
ロール管理
ボット管理モジュール
登録
ユーザーの招待
招待状の一括送信
ユーザーデータのインポート
Active Directoryからユーザーを同期
セキュリティ/コンプライアンス
シングル サインオンの使用
セキュリティ設定
Billing(日本未対応)
  1. ホーム
  2. Docs
  3. Virtual Assistants
  4. Advanced Topics
  5. Language Management
  6. Multilingual VAs: Components & Feature Support

Multilingual VAs: Components & Feature Support

In the case of multilingual VAs, while much of the assistant’s behavior does not change with the language, the semantics does impose some restrictions. In this document we will list out the different behaviors that would be language-dependent, so you can cater for such scenarios.

This article discusses language-specific components for multilingual VAs, as well as feature support and behavior, as compared to single language assistants. 

This article lists the VA elements for which you can provide language-specific values. You need not translate Standard Responses as the Platform automatically translates them when you enable a language.

Metadata

JSON object consisting of the following translatable elements

FIELD NAME

TYPE

DESCRIPTION

Bot Name

String

Name of the assistant

Bot Description

String

Description of the assistant

Bot Synonyms

Object

Arrays of important words in the task names and their corresponding synonyms. Enter translation of the words as well as their synonyms. Refer to Managing Synonyms to learn more about bot synonyms.

Bot Error Codes

Object

Arrays of error codes and their corresponding messages. Enter translations of the error message. Refer to Customizing Error Messages to learn more about error messages.

Dialog Tasks

JSON object consisting of the following translatable components of your VA’s Dialog Tasks.

FIELD NAME

TYPE

DESCRIPTION

Dialog Task Name

String

Name of the dialog task

Dialog Task Desc

String

Description of the dialog task

Dialog Task Upgrade Message

String

Message displayed to the developer on the History page for the upgraded task

Dialog Components

JSON object consisting of the following translatable components related to the NLP settings of a dialog task.

FIELD NAME

TYPE

DESCRIPTION

Dialog Component Intent

String

Name of the User Intent node

Dialog Component Description

String

Description of the User Intent node

Dialog Component Synonyms

Object

Synonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.

Dialog Component Patterns

Object

Patterns for the User Intent and Entity nodes in the dialog task. Refer to Managing Patterns to learn more.

Message Templates

JSON object with arrays of Message Template IDs and Message Template Text values. They correspond to the User Responses field in the Message node and the Bot Prompts and Error Prompts fields in the Entity node of the dialog tasks.

FIELD NAME

TYPE

DESCRIPTION

Message Template Text

String

The text entered in User Responses, Bot Prompts, or Error Prompts fields in any Message or Entity node of a dialog task.

Alert Task

JSON object consisting of the following translatable components of your assistant’s Alert Tasks.

FIELD NAME

TYPE

DESCRIPTION

Alert Name

String

Name of the alert task

Alert Short Desc

String

Description of the alert task

Alert Keywords

Array

The search keywords entered for the alert task

Alert Patterns

Array

Array of patterns related to the alert task’s name. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.

Alert Field Synonyms

Object

Arrays consisting of synonyms for each task field. Replace the field name and the synonyms with the translated text. Refer to Managing Synonyms to learn more.

Alert Field Patterns

Object

Arrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.

Alert Ignore Words

Array

Arrays of ignore words related to the alert task. Replace the words with the translated text. Refer to Managing Ignore Words and Field Memory to learn more.

Alert Upgrade Short Message

String

Upgrade short message related to the alert task.

Alert Upgrade Long Message

String

Upgrade long message related to the alert task.

Alert Query Fields

Object

Arrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.

Alert Payload Fields

Object

Arrays consisting of key-value pairs of Alert Payload fields. Replace the text with the translated text.

Alert Fields

JSON object consisting of the following translatable components in the API Request tab of the Alert task.

FIELD NAME

TYPE

DESCRIPTION

Alert Field Title

String

The title of the user input field related to the alert task, for example, Choose city

Alert Field Help

String

The help text displayed below the field title to describe the task, for example, Which city would you like to get weather alerts for?

Alert Field Placeholder

String

The placeholder text displayed inside the field.

Bot Filters

JSON object consisting of the following translatable components related to Bot filters

FIELD NAME

TYPE

DESCRIPTION

Filter Name

String

Name of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form

Field Name

Type

Description

IDP Form Field

String

Name of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

We have seen in this document, how Patterns can be used for Intent detection and Entity extraction. These rules are for VAs in the English language. In other languages, there may be differences. 

Patterns can be used in Small Talk (while defining queries), Knowledge Graph (using alternate question fields), and Trait identification but their behavior might differ slightly. The table below provides an overview of how this may occur.

PATTERN SYNTAX

INTENT DETECTION AND ENTITY EXTRACTION

SMALL

TALK

TRAITS

KNOWLEDGE

GRAPH

 

SUPPORTED IN LANGUAGES

NOT SUPPORTED IN LANGUAGES

     

word1 word2 … wordn

This mandates all the words defined to be available in the user utterance in the same consecutive order with additional words allowed in between, before and after

All languages

Yes

Yes

Yes

word1_word2

Enforce phrase, no additional words allowed in between word1 and word2.

All languages

Yes

Yes

Yes

word1 * word2

0 to infinite number of additional words between the specified words/phrases

All languages

Yes

Yes

Yes

word1 *n word2

Exactly n number of additional words between the specified words/phrases

All languages

Yes

Yes

Yes

word1 *0 word2

To disable wildcards between two tokens.

All languages

Yes

Yes

Yes

word1 < word2

Indicates the match for word2 should start from the beginning of a sentence.

All languages

Yes

Yes

Yes

word1 > word2

Indicates the end of the sentence and no words are allowed after it.

All languages

Yes

Yes

Yes

!abc

Indicates the word/concept “abc” should not exist anywhere in the user utterance after this token

All languages

Yes

Yes

Yes

!!abc

The very next word/concept should not be “abc”

All languages

Yes

Yes

Yes

[ … ]

Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].

All languages

Yes

Yes

Yes

{ … }

Used to define an optional group or words/concepts and the match would be against zero or one of the words/patterns declared in { }.

All languages

Yes

Yes

Yes

( … )

contain a pattern i.e when a pattern or part of a pattern is enclosed in these parentheses, we treat it as a pattern unlike [ ] and { }.

All languages

Yes

Yes

Yes

<< … >>

Used to find words in any order

All languages

Yes

Yes

Yes

‘word1

If you quote words or use words that are not in canonical form, the system will restrict itself to what you used in the pattern

English,

German,

Spanish,

French

Portuguese(Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

No

No

No

System Concepts

Support for built-in concepts

English,

German,

Spanish,

French

Portuguese(Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

No

No

No

Developer concepts

Support for developer-defined concepts

English,

German,

Spanish,

FrenchPortuguese(Brazilian)*,

Italian*,

Chinese simplified*,

Chinese traditional*,

Indonesian*,

Korean*,

Dutch*,

Japanese*,

Arabic*,

Finnish*,

Russian*,

Polish*,

Ukrainian*,

Swedish*,

Kazakh*,

Norwegian*,

Hindi*,

Telugu*,

Tamil*,

Marathi*,

Catalan*

Yes

Yes

Yes*

Two-letter identifiers for Dates

Like Mo for Monday, Tu for Tuesday, etc

English,

German,

Spanish,

Portuguese(Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

French,

Telugu,

Tamil,

Marathi,

Catalan

No

* in these cases, developer concepts are not supported in entity extraction

NLP Support

Here are the NLP features supported by Multilingual VAs:

NLP FEATURE

SUPPORTED IN LANGUAGES

NOT SUPPORTED IN LANGUAGES

SMALL TALK

TRAITS

KNOWLEDGE GRAPH

List of Values

         

Full Match

All languages

No

Partial Match

All languages

No

Exact Match

All languages

No

Ambiguity behavior

All languages

No

Ambiguity with multi-item selection

English

Not supported in any language except English

No

Spell Correction

English,

German,

Spanish,

French,

Portuguese(Brazilian),

Italian,

Indonesian,

Korean (from ver7.3),

Dutch,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian

Chinese simplified,

Chinese traditional,

Japanese,

Hindi,

Telugu,

Tamil,

Marathi

Yes

Amend Entities

English

Not supported in any language except English

Yes

Sentiment Analysis

English,

German,

Spanish,

French,

Dutch,

Korean (from ver7.3),

Japanese (from ver8.0),

Russian (from ver8.0),

Kazakh (from ver8.0),

Norwegian

Portuguese(Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Arabic,

Finnish,

Polish,

Ukrainian,

Swedish,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

Yes

Bot Synonyms (default)

English,

German,

Spanish,

French

Portuguese(Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh

Yes

Knowledge Graph

         

Patterns

All Languages

Yes

Search in Answer

English,

German (from ver7.3),

Spanish (from ver7.3),

French (from ver7.3),

Portuguese(Brazilian) (from ver7.3),

Italian (from ver7.3),

Indonesian (from ver7.3),

Dutch (from ver7.3),

Finnish (from ver7.3),

Polish (from ver7.3),

Swedish (from ver7.3),

Chinese simplified,

Chinese traditional,

Korean,

Japanese,

Arabic,

Russian,

Ukrainian,

Kazakh

Yes

Spell Correction

English,

German,

Spanish,

French,

Portuguese(Brazilian),

Italian,

Indonesian,

Korean,

Dutch,

Arabic,

Finnish,

Polish,

Swedish,

Ukrainian

Russian (from ver8.0),

Kazakh (from ver8.0),

Japanese (from ver8.0),

Chinese simplified,

Chinese traditional,

Catalan

Yes

Special Character support

All languages except English

English

Yes

NL Engines

         

Dependency Parser Model

German (from ver7.3),

French (from ver7.3),

Italian (from ver8.0)

English,

Spanish,

Portuguese(Brazilian),

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

メニュー