New in 18.0.2 If you see the case
type value displayed as <Undefined> in some activity dashboards, create a
scripted field to replace the predefined field for the display name of the case type.
About this task
- Problem
- The case type value is shown as <Undefined> in Case activity dashboards.
This problem does not occur in searches or index patterns.
- Cause
- This error might occur if you use a new version of the dashboards with an old version of the
Case event emitter, for example if you use Business Automation Insights 18.0.2 dashboards with an emitter
from an older IBM® Business Automation
Workflow version.
- Solution
- Create a new scripted field and use it in the activity dashboards. The following steps take the
Activities in progress dashboard as an example.
Procedure
- In the Kibana navigator, click .
- From the list of index patterns, select the case-summaries* pattern.
- Click the Scripted Fields tab for this pattern.
- Click Add Scripted Field.
- Enter a name for the scripted field.
Example: case-type-display-name-scripted
- From the Language menu, keep the painless default
value.
- From the Type menu, select string.
- Keep the default format.
- In the Script box, for the display name of the case type to be computed
on the fly from your index data, enter the following expression.
if ((doc.containsKey('case-type-display-name.keyword')) && !(doc['case-type-display-name.keyword'].empty))
{
return doc['case-type-display-name.keyword'].value
}
else
{
return doc['case-type-name.keyword'].value
}
- Click Create field.
- Click the Refresh field list button . Ignore the warning.
- In the Kibana navigator, click Visualize, then select
Activities in progress.
- Under , expand Split Series.
- From the Field menu, select your custom scripted field,
case-type-display-name-scripted in this example, to replace
case-type-display-name.keyword.
You will probably find it at the bottom of the field list.
- Click the Apply changes button .
- Save the visualization.
- Repeat the same steps to replace the case-type-display-name field with
your scripted field in all the visualizations where the error occurs.