Skip to content

Commit

Permalink
# Fixing typos on NodeJs README
Browse files Browse the repository at this point in the history
  • Loading branch information
maurok committed Jun 2, 2017
1 parent e7d60d0 commit e6d387d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Node/blog-LUISActionBinding/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,16 +77,16 @@ Bot: When do you want to check-out?

#### Scenario #3 : Trigger a Contextual Action with no previous Context (ie. from scratch)

The user can provide an input that will trigger a contextual action (with no current context). The framework supports this scenario by providing a way to instantiate the contexts chain for it (ie. the chain of parent actions that provides will provide the whole context), and finally executes the request.
The user can provide an input that will trigger a contextual action (with no current context). The framework supports this scenario by providing a way to instantiate the contexts chain for it (ie. the chain of parent actions that will provide the whole context), and finally executes the request.

Next, there is a sample to depict the scenario:

Scenario shows an user changing a check-in date within its reservation (stored in a booking system)

````
User: Please change my check-in date to tomorrow
Bot: Ok, I changed the check-in date to tomorrow -- This triggered the `ChangeHotelCheckin` intent which should run in the context of the `FindHotel` action (so main action also is instanced)
Bot: I changed you reservation in Madrid from 03/25 to 03/27 -- The required parameters of the main context are iterated until it can call the action fulfillment
Bot: Ok, I changed the check-in date to tomorrow -- This triggered the `ChangeHotelCheckin` intent which should run in the context of the `HotelReservation` action (so main action also is instanced)
Bot: I changed your reservation in Madrid from 03/25 to 03/27 -- The required parameters of the main context are iterated until it can call the action fulfillment
````

The framework also provides, within this scenario, a callback that you can use to hydrate or re-create the parent contexts for the action you are starting. So, for example, in case you have a booking system and you want to change a parameter within a 'PerformBooking' reference (main intent), you can have a related intent 'PerformBookingCheckinChange' which runs in the context of the previous one and if the user already has a reservation you can hydrate the context back from the repository where you stored it (more details about this specific scenario through the document).
Expand Down

0 comments on commit e6d387d

Please sign in to comment.