QueryTableData
This is the method that you are using
| | Parameters | As explained in the previous table | | Result Type |ListOfRecords (Auto Selected)
It indicates that the method can return one or more records
| | Record Limit |Numeric value (e.g. 10)
If Method is returning larger number of records, then you can limit this result by providing this value.
| | Record JsonPath |Each method returns data in json format and to pick any specific information from the json, we need to specify the Record JsonPath so Voice Worx platform will pick that data in consideration while displaying results.
Example: $.\[\*]
This selects all the records that is returned.
| | Empty Result Template |When the method does not return any data, this response will be generated. So we can specify something like:
“Sorry, I could not find the contact details”
| | Record Template |Let’s assume that the following json represents one record.
\[
{
"FullName": "Sandeep",
"Phone": "9851032937",
"Address": "Kathmandu, Nepal"
}
]
In this example, Phone is at root level and can be accessed by {{Phone}}
So record template can be written as
Phone number of {{FullName}} is {{Phone}}
So, when a method is executed, this will be displayed as,
Phone number of Sandeep is 9851032937
Note:
Anything written in between {{ }} is represented as a json field and it’s case-sensitive.
{{Phone}} is not same as {{phone}}
| | Result Template |This indicates how method results should be represented.
Here you go, {{Records}}
Here, {{Records}} represents one or more records separated by a separator.
| #### Sample Response: \[ { "FullName": "Sandeep", "Phone": "9851032937", "Address": "Kathmandu, Nepal" } ] L,90k After you’ve successfully completed the method, you can test to check the method functionality. Click on Save and Test, provide the parameters and click on Test. You shall see results as shown below: ### Create Intents In the top menu tabs, select “**Intents**” and “**Create New Intent**”. Then select or enter the following: **Name:** FindDataIntent **Intent Type:** Search **Intent Action:** Execute Method **DataSource:** Honeycode DS **DataSource Method:** FindData **Click:** Save ### Create Slots In the top menu tabs, select “**Slots**” and select “**Create New Slot**”. Note the Reprompt message is what Alexa will ask if it can’t fill/resolve the person slot. Then select or enter the following: **Name:** FullName **Slot Order:** 1 **Reprompt Message:** what’s the contact name **Type:** Full name **Custom Skill:** Honeycode **Intent:** SearchContactIntent **Click:** Save ### Create Utterance In the top menu tabs, select “**Utterance**” and select “**Create New Utterance**”. Utterance are words spoken to launch specific intents. Now input or select the following: **Value:** find phone number of {FullName} **Custom Skill:** Amazon HoneyCode **Intent:** SearchContactIntent **Click:** Save ### Create Input In the top menu tabs, select “**Input**” and select “**Create New Input**”.Then input or select the following: **Name:** FindDataInput **Custom Skill:** Amazon Honeycode **Custom Intent:** FindDataIntent **Data Source:** Honeycode DS **Data Source Method:** FindDataMethod ### After the input has been created, we have to create Input Parameters against every slot in the method. Add new Input Parameter and add the following details. ### **Publish to Alexa** To publish to Alexa,select “**Publish**” in the top menu tabs then click “**Add App Publishing**”. Then input or select the following: | **External Skill Name**: Contact Finder Honeycode Skill. (This will be the name of the skill in Alexa. Therefore, make it unique and different from the names of your other skills in Alexa.) | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Skill Type**: Search | | **Channel**: Alexa | | **Skill Invocation Name**: contact finder demo. (This will be what users say to launch your skill in Alexa. It must be in lower case alphabets cannot contain **START, BEGIN, STOP, EXIT, LAUNCH** and cannot contain number or special characters.) | | **Uncheck the following**: Require account linking, Auto Publish | | **Optional**: Replace all placeholder values in all “Message”. Uncheck all the settings shown in the second image below. | | **Click**: Save | . In the top menu tabs select “**Publish**” then click “**Publish to Alexa**”. Once in Publish Skill to Amazon Alexa select and do the following: **Selected Skill**: Contact Finder Honeycode skill **Select Amazon Account:** LWA Config Select the LWA account setup by your admin or the one you set up in step 4 above. **Click**: Publish To Alexa On the resulting screen, ensure that a success message shows for the publishing steps before clicking the “**Go To Alexa Skill**”. If success message not shown, click “**Go To Skill Publishing**” to fix any issue shown in publishing result. On the Alexa skill page, ensure “**Full Build Successful**” message is shown in bottom right corner before starting to test skill. Go to “**test**” tab in the top menu, then below “**test**” tab change the skill test status from “**Off**” to “**Development**”. Invoke skill by typing “**open**” followed by invocation name “**contact finder demo**” inserted in the publishing step in Voiceworx. If the invocation is successful, your configured welcome message will be displayed in the developer console. Try with an utterance that you created. “**find a contact**”. You should see a response like one below, if your honeycode table has some data. Congratulations! You have successfully completed building a Custom Skill and publishing to Alexa. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ixhello.com/ixhc/connections/amazon/amazon-honeycode.md?ask=