Communicator history
The communicator history component will show you the most recent tickets for the last 6 months. Clicking on it will navigate to the ticket
Data adapter components
Smart viewer
- The data viewer will try to render your data as clean as possible.
-
Tokens can you be used across the dataset to fill in with state-data
-
PropertyName will be rendered as "property name"
- urls will be rendered as button with a clickout Tick will check on the following querystring parameters in the url to add behaviour:
- target=new => opens the url in a new tab
example: htttp://www.yoururl.com/orders/redeem?target=new
when target=new is not found a popup will be rendered and listened to the following querystring params - width=500 => width of the opened popup to 500 if not specified it will default to 700 - height=700 => width of the opened popup to 700 if not specified it will default to 700
example: htttp://www.yoururl.com/orders/redeem?width=800&height=1000
Showing content without a label
The smart viewer can also hide the label as this is sometimes not needed to be shown. Use 'no_label_youpropertyname' to hide a label for a specific property.
Example:
{
id: 'this will not be shown because the property name is "id"',
no_label: 'while no_label is hidden, the content of the property value will be shown',
name: 'this is visible with the label "name"',
age: 58,
children: [
{
name: 'barbie',
age: 33,
},
{
name: 'ken',
age: 28,
},
]
}
Debug viewer
This viewer will present you the data that otherwise would be rendered on screen, it allows you to debug the data if needed.
List viewer
The list viewer will try to present the data as a list. It is required that the data is in the syntax of:
[
{
id: "id_1",
title: "your-title",
subtitle: "your subtitle",
},
{
id: "id_2",
title: "your-{{communicator.name?communicator}} name",
subtitle: "your subtitle",
}
]