Hi Everyone, I’m loving Rasa. Most things have been going well. However, despite two days of trying and searching, I’ve had no luck with this seemingly common issue. The goal is to simply deactivate a form on command. A user activates form by typing “create use case”. But if in the middle the user decides to exit (cancel), I can’t seem to get it to work. I have an intent - stop_form. I’m using stop_form to trigger an utterance that ask if they are sure. If the response is affirmed, then the form should be deactivated. For clarity, I’ve listed all relevant parts of this process from the nlu, domain and stories files. Any help is appreciated. Can’t trigger the intent. I’m using Rasa 2.0 #domain.yml intents: - stop_form: use_entities: [] slots: usecase_id: type: text influence_conversation: false user_id: type: text influence_conversation: false user_name: type: text influence_conversation: false responses: utter_ask_continue: - text: Do you want to continue? Yes or No... forms: use_case_form: use_case_name: - type: from_text use_case_description: - type: from_text use_case_note: - type: from_text #nlu.yml - intent: stop_form examples: | - please stop this form - stop form - I want to stop form - I don't want to continue this form - please cancel form - intent: affirm examples: | - yes - y - sure - absolutely - definitely - cool - indeed - of course - that sounds good - correct - ye - uh yes - let's do it - yeah - uh yes - um yes - yes knocking - that's correct - yes yes - right - yea - yes right - yes and i dont care - right on - i love that - intent: deny examples: | - no - naaaa - never - I don't think so - don't like that - no way - not really - no new selection - no thanks - no thank you - uh no - breath no - do you have something else - no this does not work for me - heck no! - hell no #stories.yml - story: stop use case form + continue #happy path steps: - intent: create_use_case - action: use_case_form - active_loop: use_case_form - intent: stop_form - action: utter_ask_continue - intent: affirm - action: use_case_form - active_loop: null - action: action_submit_use_case - action: utter_submit_use_case - story: stop use case form + stop #unhappy path - stop form steps: - intent: create_use_case - action: use_case_form - active_loop: use_case_form - intent: stop_progress - action: utter_ask_continue - intent: deny - action: action_deactivate_loop - active_loop: null

Ok, special thanks to @nik202 for helping me to get through all of this. While I’ve seen a lot of posts regarding form deactivation, I’ve never seen one solution that consistently worked. I think that maybe I’ve found that solution. If so, hopefully this will help everyone out there who is struggling with form deactivations. Note: This example is SUPER simple. And while I’m actually on Rasa 2.8 (rasa_sdk 2.8) it should be backwards compatible. Below I’ll list the example by files (nlu.yml, domain.yml, rules.yml and actions.py). For the actions, I only listed the custom action that stops the form - to keep things simple. Again, this is the only solution that I’ve been successful with each time. The form has 3 slots: company_location, company_name and company_source. If a user wants to exit the form they type ‘halt’, which is associated with the stop_company_form intent. This prompts the execution of the action_stop_company_form custom action, which deactivates the form and clears all the slots. #nlu.yml ################## nlu: - intent: stop_company_form examples: | - halt - halt halt - I'm halting - halt halt halt - intent: create_company examples: | - i want to create a company - let's setup a company - add company #domain.yml ################## intents: - stop_company_form: use_entities: [] - create_company: use_entities: [] slots: company_location: type: text auto_fill: false influence_conversation: false company_name: type: text auto_fill: false influence_conversation: false company_source: type: text auto_fill: false influence_conversation: false actions: - action_submit_company - action_stop_company_form forms: company_form: ignored_intents: - stop_company_form required_slots: company_location: - type: from_text company_name: type: from_text company_source: - type: from_text #rules.yml ################## rules: - rule: Activate Company Form steps: - intent: create_company - action: company_form - active_loop: company_form - rule: Stop Company Form steps: - intent: stop_form - action: action_stop_company_form - action: action_deactivate_form #deactivates form - active_loop: null #kills loop #actions.py ################## class StopCompanyForm(Action): def name(self) -> Text: return "action_stop_company_form" def run( self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: Dict[Text, Any], ) -> List[Dict[Text, Any]]: #Utters message to inform user form has been cancelled dispatcher.utter_message(text="Company Form Canceled!") #Clears slots return[SlotSet(SlotSet("company_location", None),SlotSet("company_name", None),SlotSet("company_source", None)]

When I use the following command to start rasa… rasa run -m models --enable-api --cors “*” everything loads and then it gives the following message: The client is using an unsupported version of the Socket.IO or Engine.IO protocols (further occurrences of this error will be logged with level INFO)

I spent two days trying to get this issue worked out, but had no success. Everything in the forum spoke of a socketio version mismatch with the rasa-webchat but nothing was clear in the way of how to solve it. The only thing that worked was downgrading back to versions 2.0

I literally tried every variation of python-socketio and python-engineio. It became a source of consternation.

And this is the rasa-webchat widget code… index.html (1005 Bytes)

I think it’s liked to this… [image] Rasa 2.x socketio not working! Rasa Open Source I have been runnning my chatbots with Rasa 1.10 version, now I started to test Rasa 2.4 version. Using shell worked, but when using full system with webchat as chatbot widget, it didn’t work. I made some testing and found that Rasa 2.4 doesn’t initialise socket connection. in credentials file I have socketio: user_message_evt: user_uttered bot_message_evt: bot_uttered session_persistence: true So if I start Rasa docker with this command docker run --name=rasa1 --user 1…

What’s wrong with the rasa-webchat code? It works for Rasa 2.0 rasa_sdk 2.0. In fact, I was just able to get Rasa 2.3 and rasa_sdk 2.3.1 to work with it as well.

@eaofcc You are able to run on localhost? or can see chat widget? able to get response?

Yes. On http://localhost:8000 and I’m able to use the chat widget with no problem. Everything works, so long as I don’t exceed rasa 2.3 and rasa_sdk 2.3.1 :slight_smile:

@eaofcc are you validating any form? I guess no right. then me bad Sorry. I withdraw my post. I think I need break today :frowning: @eaofcc your issue in mind that’s why thinking…sorry for the confusion.

Can’t get form to deactivate

Rasa Open Source

nik202 (NiK202) July 20, 2021, 6:02pm 45

@eaofcc anytime bro.

Topic		Replies	Views
Can´t deactivate rasa form if user want to stop Rasa Open Source	4	2026	April 22, 2020
Rasa Form deactivation broken Rasa Open Source	5	745	November 16, 2019
Form deactivate not work Rasa Open Source	4	560	September 7, 2021
Action_deactivate_form not working Rasa Open Source	17	2918	November 4, 2020
Action_deactivate_form is not working Rasa Open Source	5	605	December 22, 2020

Can’t get form to deactivate

Related topics