Hi Marija,
From my understanding, AVA cannot arbitrarily populate End Context variables purely from the conversation unless the value is explicitly mapped from either:
- a tool/action result
- or an existing Start Context variable
The conversational reasoning itself does not automatically persist values into End Context.
So if you create a Start Context variable and expect the AVA to dynamically assign/update it during the conversation without a tool/action involved, it will typically remain NOT SET.
In practice, the common pattern is:
- collect/extract the information during the conversation
- pass it through a tool/action
- map the returned value into the End Context variable
At the moment, I don't believe there is native support for directly persisting arbitrary conversational state into End Context variables without that intermediary mapping/action step.
------------------------------
Gabriel Garcia
NA
------------------------------