Output Templating

Search…
Output Templating
One of the coolest features of EDDI is it will allow you dynamically template your output based on data that you would receive from httpCalls or context information for instance, that makes EDDI's replies to user interactions richly and dynamically.
The output templating is evaluated by thymeleaf templating engine, that means you can use the majority of thymeleaf tags and expression language to define how you would like your output to be.
Enabling the feature:
Basically while creating the bot you must include eddi://ai.labs.output to one of the packages that will be part of the bot.
Important: The templating feature will not work if it is included before eddi://ai.labs.output extension, it must be included after.
Example
Here is how the output templating should be specified inside of a package.
1
{
2
  "type": "eddi://ai.labs.templating",
3
  "extensions": {},
4
  "config": {},
5
  "packageExtensions": [
6
    {
7
      "type": "eddi://ai.labs.parser",
8
      "extensions": {
9
        "dictionaries": [
10
          {
11
            "type": "eddi://ai.labs.parser.dictionaries.integer"
12
          },
13
          {
14
            "type": "eddi://ai.labs.parser.dictionaries.decimal"
15
          },
16
          {
17
            "type": "eddi://ai.labs.parser.dictionaries.punctuation"
18
          },
19
          {
20
            "type": "eddi://ai.labs.parser.dictionaries.email"
21
          },
22
          {
23
            "type": "eddi://ai.labs.parser.dictionaries.time"
24
          },
25
          {
26
            "type": "eddi://ai.labs.parser.dictionaries.ordinalNumber"
27
          },
28
          {
29
            "type": "eddi://ai.labs.parser.dictionaries.regular",
30
            "config": {
31
              "uri": "eddi://ai.labs.regulardictionary/regulardictionarystore/regulardictionaries/{{dictionary_id}}?version=1"
32
            }
33
          }
34
        ],
35
        "corrections": [
36
          {
37
            "type": "eddi://ai.labs.parser.corrections.stemming",
38
            "config": {
39
              "language": "english",
40
              "lookupIfKnown": "false"
41
            }
42
          },
43
          {
44
            "type": "eddi://ai.labs.parser.corrections.levenshtein",
45
            "config": {
46
              "distance": "2"
47
            }
48
          },
49
          {
50
            "type": "eddi://ai.labs.parser.corrections.mergedTerms"
51
          }
52
        ]
53
      },
54
      "config": {}
55
    },
56
    {
57
      "type": "eddi://ai.labs.behavior",
58
      "config": {
59
        "uri": "eddi://ai.labs.behavior/behaviorstore/behaviorsets/{{behaviourset_id}}?version=1"
60
      }
61
    },
62
    {
63
      "type": "eddi://ai.labs.httpcalls",
64
      "config": {
65
        "uri": "eddi://ai.labs.httpcalls/httpcallsstore/httpcalls/{{httpcall_id}}?version=1"
66
      }
67
    },
68
    {
69
      "type": "eddi://ai.labs.output",
70
      "config": {
71
        "uri": "eddi://ai.labs.output/outputstore/outputsets/{{outputset_id}}?version=1"
72
      }
73
    },
74
    {
75
      "type": "eddi://ai.labs.templating",
76
      "extensions": {},
77
      "config": {}
78
    }
79
  ]
80
}
Copied!
Additional Information :
​Thymeleaf documentation.​
Passing context information
HttpCalls
Last modified 1yr ago
Export as PDF
Copy link
Contents
Enabling the feature:
Example
Additional Information :