[Controls] [Meta] Engineering Phase 2 Implementation Roadmap

[ThomThomson]

Controls Phase 2

The following is an ordered list of tasks / PRs which need to be completed for the second phase of the controls project. By the end of this phase, deliverables will include:

• A validation system for the Options List Control to show when previously selected values would result in an empty dashboard.
  • The options list control should have a new setting to control what happens to invalid selections. Possible settings could include: Remove, Ignore, & Apply
• The ability to enable a Hierarchical Chaining mode which should be compatible with every type of control.
• A new Range Slider control
• A new Time Slider control
• A new Time Picker control
• Various upgrades to the Options List

Tasks / PRs

Options List Upgrades @ThomThomson

• Show cardinality in Options List
• Options List Static Mode For Booleans
• Options List control validation

Hierarchical Chaining System @ThomThomson

• Set up and maintain Input / Output subscription chain even when control order changes
• Propagate filtering to child filters
• Make Hierarchical Chaining optional

Range Slider @cqliu1 #125584

• Create React component in storybook
• State management
• Create Inline Editor Component
• Write embeddable and factory. Register control type

Time Slider @crob611

• Create React component in storybook
• State management
• Create Inline Editor Component
• Write embeddable and factory. Register control type

Time Picker

• Create React component in storybook
• State management
• Create Inline Editor Component
• Write embeddable and factory. Register control type

Administrative / Stability

• Telemetry / Usage tracking for Controls [Controls] Usage Telemetry  #112350
• Move Controls from Presentation Util to its own plugin

Deprecation / Migration

• Opt in Migration System [Controls] Create an Opt-In Migration System #112349
• Hide legacy controls button

POC

• Test / POC render & interact in canvas

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[ThomThomson]

We can consider adding functionality to locally filter individual controls to allow users to narrow which options are shown in the control. This could be accomplished in the generic control editor because we know all controls can inherit filters, query and time range from the dashboard. See this issue for more info

[ghudgins]

a good wildcard request from controls from discuss user - https://discuss.elastic.co/t/wildcard-search-based-on-a-field-like-splunk/295250

[ThomThomson]

A wildcard-based Search box control could be a good candidate for Controls phase 3. Basically this would be a new control type which shows only a search box, and anything written in the box would immediately be turned into a wildcard filter, without any validation.

[ThomThomson]

A Query DSL templating feature would be extremely helpful for some control types. Specifically this request could be fulfilled with an Options List control configured to insert its selection into the key portion of a terms lookup query.

[ThomThomson]

Something else to think about adding is configurable sorting for Options List controls.

Currently the sorting is handled by relevance (number of documents), but it's common for authors to want their controls sorted alphabetically.

Additionally, there have been a few requests for adding numeric sorting to the Options List control. I'm not sure if this is possible with Keyword mapped fields, but we can look into it. There are some relevant docs that might help us add this option.

[ThomThomson]

Potential feature additions for phase 2 or phase 3:

• Scripted Field support
• Frozen Index support
• Support Numeric fields in options list

[ThomThomson]

Closing this as Controls Phase 2 is finished.