Google Actions跟进多个action_intent_OPTION

Question

I've been playing around with Google Actions lately. I want to create a flow were i make a transfer. It consists of 3 steps.

On the first step user selects the amount, then the From account and last the To account.

The first intent has the transferMoney-followup output context. The second intent has the transferMoney-followup as input context and the transferMoneyFromAccount-followup as output context. The third intent has the transferMoneyFromAccount-followup as input context.

When i get from the first intent to the second one and the user selects an option i have access to the first one and the parameters from there.

When i show now the list again this time for the 3rd intent after the selection it never reaches there and the code is never executed and the 2nd intent is executed again. My guess is i'm doing something wrong with the contexts but can't figure out what.

const app = require('actions-on-google').dialogflow();
app.intent('transferMoney' , (conv, params) => {
    conv.ask("Sure, let's transfer " + params.amount +"...");
    let items = {
        title: 'Select an account to send money FROM',
        items: {}
    };
    for (let i = 0; i < conv.data.userInfo.banks[0].accountsInformation.accounts.length; i++) {
        let account = conv.data.userInfo.banks[0].accountsInformation.accounts[i];
        items.items[account.id] = {
            title: account.alias,
            description: account.balance + "$"
        }
    }
    conv.ask(new List(items));
});

//Create a Dialogflow intent with the `actions_intent_OPTION` event
app.intent('transferMoney.FromAccount', (conv, params, option) => {
    let amount = conv.contexts.get("transfermoney-followup").parameters.amount;
    let fromAccountId = option;
    conv.ask("Let's send that " + amount + " from " + fromAccountId);
    conv.ask("Where should we send them to ?");
    let items = {
        title: 'Select an account to send money TO',
        items: {}
    };
    for (let i = 0; i < conv.data.userInfo.banks[0].accountsInformation.accounts.length; i++) {
        let account = conv.data.userInfo.banks[0].accountsInformation.accounts[i];
        items.items[account.id] = {
            title: account.alias,
            description: account.balance + "$"
        }
    }
    conv.ask(new List(items));
});

//Create a Dialogflow intent with the `actions_intent_OPTION` event
app.intent('transferMoney.FromAccount.ToAccount', (conv, params, option) => {
    let amount = 0;
    let fromAccountId = 1;
    let toAccountId = 2;
    conv.ask("Let's send that " + amount + " from " + fromAccountId + " to " + toAccountId)
});

Let me know if you need any more information.

EDIT: 1st intent 2nd intent 3rd intent

Answer 1

The issue is that the lifespan of your two contexts are 2. This means that they will exist for two more replies from the user. So your "transferMoney-followup" and "transferMoneyFromAccount-followup" contexts are both valid at the same time. When faced with this, Dialogflow ends up picking the first one that matches the criteria, and ends up going with the "transferMoney.FromAccount" Intent.

You have a few solutions.

The first is the easiest - reduce the lifespan to 1. This, however, has a couple of side-effects:

• If the user says something that is handled with a Fallback Intent or that otherwise doesn't match, the Context will run out of time.

• The parameters that were stored with the first Context are lost by the time you get to the third Intent.

A little more difficult, but probably better is to handle these in your fulfillment code. You'd need to do the following in the intent handler for "transferMoney.ForAccount":

• Copy all the values you need into the transferMoneyFromAccount-followup context (or any other context with a long enough lifespan) and make sure the lifespan is set for "long enough". You can even make this fairly long.

• Set the lifespan for transferMoney-followup to 0. This will clear it out so it won't be caught the next time the user says something.

Depending on your needs, it might be wise to do the same sort of thing for your other intent handlers as well.