# \[Solved\] RASA FormPolicy

**URL:** <https://forum.rasa.com/t/solved-rasa-formpolicy/11379>\
**Category:** Rasa Open Source\
**Created:** [June 12, 2019, 1:28pm UTC](https://forum.rasa.com/t/solved-rasa-formpolicy/11379 "2019-06-12T13:28:21Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![JulianGerhard](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/juliangerhard/32/3781_2.png) [@JulianGerhard](https://forum.rasa.com/u/JulianGerhard)\
**Post date:** [June 13, 2019, 7:00am UTC](https://forum.rasa.com/t/solved-rasa-formpolicy/11379/8 "2019-06-13T07:00:09Z")

</div>

Okay, could you please do an experiment:

1. Backup your stories.md and empty it afterwards. Fill in:

- book\_appointment

- book\_appointment{“doctor\_name”: “Lubab”}

1. Modify domain.yml:

Change:

```
doctor_name:
    type: text

```

to

```
doctor_name:
    type: "unfeaturized"
    auto_fill: 0

```

1. Change slot mapping

Change

```
return {
    "doctor_name": [
        self.from_text()
    ]
}

```

to

```
return {
    "doctor_name": [
        self.from_entity(entity="doctor_name")
    ]
}

```

1. Retrain
2. Start Action Server and Rasa an say: a. I want to visit a doctor -\> Luba b. I want to visit Lubab

and tell me about the results.

---

_[View the full topic](https://forum.rasa.com/t/solved-rasa-formpolicy/11379)._
