A widget is a term used to represent an atomic UI element associated with specific data.
It serves as a versatile tool that adds context based on the trace state.
Its primary objective is to deliver meaningful insights to end users, offering a clear understanding of the progress made in the process.Since users may have varying preferences for the information displayed,
it is essential to create a configuration file aligned with the principles used for the overview table configuration.
A view is a keyword we use to define an atomic display of a piece of data. We provide core views which are fundamental to displaying correctly various natures of data.All the views have the common property:
The text view enables to display a piece of data as plain text. If the text is too long, an ellipses will be displayed.
This is the default view used if a view type is invalid.
The JMESPath syntax is very powerful and can be used to build complex expressions.
For example, the path "['Hello ',userName,', how are you?'].join('',@)" will produce "Hello ${userName}, how are you?".
A locale string or array of locale strings that contain one or more language or locale tags.
If you include more than one locale string, list them in descending order of priority so that the first entry is the preferred locale.
A JMESPath that resolves to a number. This feature allows adding context to the displayed number by appending a ” / denominator” to it.
This is useful, for instance, when showing the number of steps completed out of a total expected.
The same format is applied to the denominator.
The date view displays a formatted date and supports a deadline warning feature. This feature displays the date in red with a warning icon if it’s past or too close to today.
A JMESPath that resolves to a string. This text will be displayed as the link content.
If no urlPath is provided or its resolved value is falsy, the resolved value of the path will also act as the link url.