I am trying to create a rule that will utter a certain response if a slot is set to true, and another otherwise. The slot is called sent_ticket and it is set by an action. A form gathers user details and calls the action_create_freshdesk_ticket, which attempts to create a ticket. Then the sent_ticket slot will be set to true or false depending on whether this succeeds or fails. This part works, and I can see the slot being set correctly. I then have 2 rules in order to have difference utterances to the user depending on the value of the sent_ticket slot. But even though I can see the sent_ticket slot being correctly filled, the utterances don’t happen. The debug output shows: rasa.core.policies.rule_policy - There is no applicable rule. Why is it not triggering the defined rule? See below rules.yml. - rule: gathered email for ticket condition: - active_loop: ticket_form steps: - action: ticket_form - active_loop: null - slot_was_set: - requested_slot: null # Actions to be run after form is submitted - action: utter_thanks - action: action_create_freshdesk_ticket wait_for_user_input: false - rule: sucessfully created ticket condition: - slot_was_set: - sent_ticket: true steps: - action: utter_created_ticket - rule: failed to create ticket condition: - slot_was_set: - sent_ticket: false steps: - action: utter_something_went_wrong

I’ve been able to get the desired behaviour: the bot utters a different response depending on whether a custom action is able to successfully create a ticket or not. @nik202 your link to the RulePolicy docs (rather than the other Rules documentation) had some examples that were very helpful, thank you again. In particular I think the main thing that had been confusing me is that in order to recognise the slot (which is text type) being set (as anything) in a rule, I had to put in a dummy string value. This was not clear to me at all - I would expect it in the nlu training data, but not the rules (it feels strange to write, I wonder if there is a better way like an “AnyText” wildcard or something). So the rule indicating a successful ticket creation looks for the string "1" as slot was set, and the alternative rule where ticket creation failed looks for null. Below a code snippet for anyone else struggling. A form gets the user email, then a custom action attempts to create a ticket - if it succeeds, it sets the slot ticket_number. The bot utters different things according to success or failure. in domain.yml: slots: email: type: text influence_conversation: true ticket_number: type: text influence_conversation: true In rules.yml: - rule: gathered email for ticket condition: - active_loop: ticket_form steps: # Form is deactivated - action: ticket_form - active_loop: null - slot_was_set: - requested_slot: null # The actions we want to run when the form is submitted. - action: action_create_ticket wait_for_user_input: false - rule: ticket created steps: - action: action_create_ticket - slot_was_set: - ticket_number: "1" - action: utter_ticket_created - action: utter_ask_something_else - rule: ticket not created steps: - action: action_create_ticket - slot_was_set: - ticket_number: null - action: utter_something_went_wrong - action: utter_ask_something_else

Conditional rule does not trigger when slot is set by action

Rasa Open Source

andres_pineiro (Andrés) May 9, 2022, 6:05am 18

Hi @justyn, thanks for you reply.

If you are interested, we just discovered that if you don’t use the initial_value the problem seems to go away. I asked about it in this post.

1 Like

Topic		Replies	Views
Triggering a rule when the user does not fill a slot Rasa Open Source	6	1525	May 7, 2022
Condition contraints on a rule - what am I doing wrong? Rasa Open Source	6	537	October 27, 2021
Can I make decisions based on slots? Rasa Open Source	3	220	August 23, 2023
Rasa not following the rules Rasa Open Source	4	246	April 22, 2021
Condition based rules is not working as expected Rasa Open Source	1	527	October 10, 2022

Conditional rule does not trigger when slot is set by action

Related Topics