It consists of following navigation tabs:
...
- Key- parameter1 and Value value1
- Key- parameter2 and Value value2
Query Parameters
The query parameters are sometimes referred to as optional parameters. The query parameters are separated from the hierarchical parameters by the question mark. Query parameters appear in the URL after the question mark (?) after the resource name:
https://myserver.com/resource-name?param1=value1¶m2=value2
...
Title: Title of the output data. Information to show can be based on the output of the payload as shown below if Ticket ID needs to be shown as Title along with a description. Example: Ticket For example, Ticket #@resp.data.items.TicketIdentifier @resp.data.items.Description
While parsing JSON response, the variables of attribute names or keys having special characters (such as space, period, hyphen and others), are truncated. To resolve this issue, enclose the advanced expressions (having spaces) between $\{ and \} and also support the older way of writing the expression in the same sentence.
Example: To avoid truncating details for the following sample JSON response, do the following:
{
"entries": [
{
"values": {
"Entry ID": "INC000000867505",
"Submitter": "peter.hinchey",
"Submit Date": "2018-12-17T16:12:39.000+0000",
"AEC Initial Assignee": "Roman Havryshkiv",
"Assignee Login ID": "v-havryshr"
}
}
]
}
Add ${@response.key with spaces}
The above sample will be parsed as shown below:
${@resp.entries.values.Entry ID}
${@resp.entries.values.Submit Date}
${@resp.entries.values.AEC Initial Assignee}
${@resp.entries.values.Assignee Login ID}
Sub Title: Subtitle of the output data, In the below example, we are showing the information Ticket status, Priority, AssignedIndividual and Requestor.
...
Payload: Data type payload.
- Click Save to reflect the Web Services in Luma Bot or else click Cancel.