These docs are for version 1.x of Rasa Open Source.

### User Guide

- [Installation](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/installation/)
- [Tutorial: Rasa Basics](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/rasa-tutorial/)
- [Tutorial: Building Assistants](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/building-assistants/)
- [Command Line Interface](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/command-line-interface/)
- [Architecture](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/architecture/)
- [Messaging and Voice Channels](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/messaging-and-voice-channels/)
- [Evaluating Models](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/evaluating-models/)
- [Validate Data](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/validate-files/)
- [Configuring the HTTP API](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/configuring-http-api/)
- [Deploying your Rasa Assistant](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/how-to-deploy/)
- [Cloud Storage](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/cloud-storage/)

### NLU

- [About](https://legacy-docs-v1.rasa.com/1.7.4/nlu/about/)
- [Using NLU Only](https://legacy-docs-v1.rasa.com/1.7.4/nlu/using-nlu-only/)
- [Training Data Format](https://legacy-docs-v1.rasa.com/1.7.4/nlu/training-data-format/)
- [Choosing a Pipeline](https://legacy-docs-v1.rasa.com/1.7.4/nlu/choosing-a-pipeline/)
- [Language Support](https://legacy-docs-v1.rasa.com/1.7.4/nlu/language-support/)
- [Entity Extraction](https://legacy-docs-v1.rasa.com/1.7.4/nlu/entity-extraction/)
- [Components](https://legacy-docs-v1.rasa.com/1.7.4/nlu/components/)

### Core

- [About](https://legacy-docs-v1.rasa.com/1.7.4/core/about/)
- [Stories](https://legacy-docs-v1.rasa.com/1.7.4/core/stories/)
- [Domains](https://legacy-docs-v1.rasa.com/1.7.4/core/domains/)
- [Responses](https://legacy-docs-v1.rasa.com/1.7.4/core/responses/)
- [Actions](https://legacy-docs-v1.rasa.com/1.7.4/core/actions/)
- [Policies](https://legacy-docs-v1.rasa.com/1.7.4/core/policies/)
- [Slots](https://legacy-docs-v1.rasa.com/1.7.4/core/slots/)
- [Forms](https://legacy-docs-v1.rasa.com/1.7.4/core/forms/#)
- [Retrieval Actions](https://legacy-docs-v1.rasa.com/1.7.4/core/retrieval-actions/)
- [Interactive Learning](https://legacy-docs-v1.rasa.com/1.7.4/core/interactive-learning/)
- [Fallback Actions](https://legacy-docs-v1.rasa.com/1.7.4/core/fallback-actions/)
- [Knowledge Base Actions](https://legacy-docs-v1.rasa.com/1.7.4/core/knowledge-bases/)

### Conversation Design

- [Dialogue Elements](https://legacy-docs-v1.rasa.com/1.7.4/dialogue-elements/dialogue-elements/)
- [Small Talk](https://legacy-docs-v1.rasa.com/1.7.4/dialogue-elements/small-talk/)
- [Completing Tasks](https://legacy-docs-v1.rasa.com/1.7.4/dialogue-elements/completing-tasks/)
- [Guiding Users](https://legacy-docs-v1.rasa.com/1.7.4/dialogue-elements/guiding-users/)

### API Reference

- [Action Server](https://legacy-docs-v1.rasa.com/1.7.4/api/action-server/)
- [HTTP API](https://legacy-docs-v1.rasa.com/1.7.4/api/http-api/)
- [Jupyter Notebooks](https://legacy-docs-v1.rasa.com/1.7.4/api/jupyter-notebooks/)
- [Agent](https://legacy-docs-v1.rasa.com/1.7.4/api/agent/)
- [Custom NLU Components](https://legacy-docs-v1.rasa.com/1.7.4/api/custom-nlu-components/)
- [Rasa SDK](https://legacy-docs-v1.rasa.com/1.7.4/api/rasa-sdk/)
- [Events](https://legacy-docs-v1.rasa.com/1.7.4/api/events/)
- [Tracker](https://legacy-docs-v1.rasa.com/1.7.4/api/tracker/)
- [Tracker Stores](https://legacy-docs-v1.rasa.com/1.7.4/api/tracker-stores/)
- [Event Brokers](https://legacy-docs-v1.rasa.com/1.7.4/api/event-brokers/)
- [Lock Stores](https://legacy-docs-v1.rasa.com/1.7.4/api/lock-stores/)
- [Training Data Importers](https://legacy-docs-v1.rasa.com/1.7.4/api/training-data-importers/)
- [Featurization of Conversations](https://legacy-docs-v1.rasa.com/1.7.4/api/core-featurization/)
- [Migration Guide](https://legacy-docs-v1.rasa.com/1.7.4/migration-guide/)
- [Rasa OSS Change Log](https://legacy-docs-v1.rasa.com/1.7.4/changelog/)

### Migrate from (beta)

- [Dialogflow](https://legacy-docs-v1.rasa.com/1.7.4/migrate-from/google-dialogflow-to-rasa/)
- [Wit.ai](https://legacy-docs-v1.rasa.com/1.7.4/migrate-from/facebook-wit-ai-to-rasa/)
- [LUIS](https://legacy-docs-v1.rasa.com/1.7.4/migrate-from/microsoft-luis-to-rasa/)
- [IBM Watson](https://legacy-docs-v1.rasa.com/1.7.4/migrate-from/ibm-watson-to-rasa/)

### Reference

- [Glossary](https://legacy-docs-v1.rasa.com/1.7.4/glossary/)

### Forms

#### Note

There is an in-depth tutorial [here](https://blog.rasa.com/building-contextual-assistants-with-rasa-formaction/) about how to use Rasa Forms for slot filling.

To use forms, you also need to include the `FormPolicy` in your policy configuration file. For example:

```yaml
policies:
  - name: "FormPolicy"
```

Using a `FormAction`, you can describe _all_ of the happy paths with a single story. By "happy path", we mean that whenever you ask a user for some information, they respond with the information you asked for.

```yaml
## happy path
* request_restaurant
    - restaurant_form
    - form{"name": "restaurant_form"}
    - form{"name": null}
```

In this story the user intent is `request_restaurant`, which is followed by the form action `restaurant_form`.

The `FormAction` will only request slots which haven’t already been set. If a user starts the conversation with I’d like a vegetarian Chinese restaurant for 8 people, then they won’t be asked about the `cuisine` and `num_people` slots.

If you want to allow a combination of these, provide them as a list as in the example above.

After extracting a slot value from user input, the form will try to validate the value of the slot. Note that by default, validation only happens if the form action is executed immediately after user input.

```python
def validate_cuisine(self, value: Text, dispatcher: CollectingDispatcher, tracker: Tracker, domain: Dict[Text, Any]) -> Dict[Text, Any]:
    """Validate cuisine value."""
    if value.lower() in self.cuisine_db():
        return {"cuisine": value}
    else:
        dispatcher.utter_message(template="utter_wrong_cuisine")
        return {"cuisine": None}
```

Of course your users will not always respond with the information you ask of them. The way this works with forms is that a form will raise an `ActionExecutionRejection` if the user didn’t provide the requested information.

The slot `requested_slot` is automatically added to the domain as an unfeaturized slot. If you want to make it featurized, you need to add it to your domain file as a categorical slot. You might want to handle your unhappy paths differently depending on what slot is currently being asked from the user.

### Debugging

Try to run your bot with the `debug` flag, see [Command Line Interface](https://legacy-docs-v1.rasa.com/1.7.4/user-guide/command-line-interface/#command-line-interface) for details. If you are just getting started, you probably only have a few hand-written stories.

👋 I can help you get started with Rasa and answer your technical questions.