Skip to content
This repository has been archived by the owner on May 28, 2024. It is now read-only.

Context is remembered of the optional parameter during slot filling of another. #402

Open
DeveloperBSHTG opened this issue Jul 29, 2020 · 0 comments

Comments

@DeveloperBSHTG
Copy link

DeveloperBSHTG commented Jul 29, 2020

Context of an optional parameter is remembered during slot filling of another required parameter. This should not happen in this use case.
image

If I try to modify the context it won't overwrite the values.

conv.contexts.set('user_product_get_brand', 1, parameters = {
      'dummy': '',
      'notAvailableBrand': '',
    });

Will result in:

{
  name: 'myProject',
  lifespan: 1,
  parameters: {
    brand: '',
    'brand.original': '',
    notAvailableBrand: 'Andrelon',
    'notAvailableBrand.original': 'Andrelon',
    dummy: ''
  }
}

The 'notAvailableBrand' shouldn't be remembered, because of dialog branching. If the user says something that is not recognized or inaudible, after being prompted to give a valid brand, the dialog flow should ask: 'Sorry, could you repeat that?'. However, that is not possible at the moment, because the 'notAvailableBrand' is remembered over multiple conversation turns.

Is there any way to forget the value of 'notAvailableBrand' on every query, while slot filling the 'brand' parameter?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant