slot_was_set doesn't work as expected for categorical slots

[behnam354]

Rasa version: 2.6.0

Python version: 3.6.8

Operating system (windows, osx, ...): ubuntu 18.04

Issue:

When defining a rule with slot_was_set conditioned on a categorical slot .. the rule is applied when slot is not null and don't really care about the category values. For example if we create a categorical slot say session_complete .. then Rasa 2.6.0 complains about the two following rules conflicting with one another:

## in rule.yml
# submit form if success
  - rule: submit my form
    condition:
    - active_loop: my_form
    steps:
    - action: my_form
    - active_loop: null
    - slot_was_set:
      - requested_slot: null
    - slot_was_set:
      - session_complete: success
    - action: action_submit_my_form


  - rule: deactivate my form and restart session if failure
    condition:
    - active_loop: my_form
    steps:
    - action: my_form
    - active_loop: null
    - slot_was_set:
      - requested_slot: null
    - slot_was_set:
      - session_complete: failure ## changing this to null resolves the conflict
    - action: action_restart

Content of domain file (domain.yml) (if relevant):

slots:
  session_complete:
    type: categorical
    initial_value: null
    auto_fill: true
    influence_conversation: true
    values:
      - null
      - success
      - failure

[sara-tagger]

Thanks for the issue, @koernerfelicia will get back to you about it soon!

You may find help in the docs and the forum, too 🤗

[koernerfelicia]

Hi @behnam354, I think this is related to a bug we fixed in 2.6.2. Could you please update your rasa version and let me know whether the problem persists?

[behnam354]

@koernerfelicia Yes that's fixed in rasa 2.6.2. Thanks!

[vmandalapu1994]

I think this bug still not fixed...With rasa:3.6.2 also I see this issue