System entities not being supported

[siddharth abhi]

If I used some system entities that is not supported by the agent's  language, will CX treat it as sys.any or will it throw exception.

How do I re use entities such as sys.unit-weight that is supported in ES but not in CX.

[siddharth abhi]

Also Why CX is able to infer sys.temperature for German when it is not supported for the same.

[Eduardo Ortiz Caraveo]

I think you will find this documentation helpful for your case.

1. https://medium.com/google-cloud/using-dialogflow-cx-composite-entities-to-work-around-system-entities-limitations-c6385df12f2b

[siddharth abhi]

Thanks for the documentation, but it doesn't answer the question how am I going to deal with unit-weight and unit speed when unit-weight-name is not supported in CX.

[Eduardo Ortiz Caraveo]

Let me search for documentation to see if I can find a workaround for the issue you are facing, in the meantime you can see the limitations that dialogflow cx has

[siddharth abhi]

Another question question related to extending system entities.

From what I gathered ,from  documentation , extending system entities requires creating new entity with display_name= "sys.color"

"display_name":"sys.unit-weight",

"kind": "KIND_LIST",

 "auto_expansion_mode": "AUTO_EXPANSION_MODE_DEFAULT",

"entities": [

{

"value": "whatever",

"synonyms": [

"whatever"

]

}

],

"enable_fuzzy_extraction": False

Questions

1. Why doesn't above request throw error when sys.unit-weight is not extendable

2. what is the use of auto_expansion_mode here, when I am extending system entity

3. Will auto_expansion_mode set to true, make my system entity ,infer values that are not provided beforehand(actual values + extended values)

4. Is the purpose of auto_expansion_mode in context of extending system entities , to make sys.entities infer values not previously provided along with providing some extra values through synonym+values array.