You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a visualization can only render information from the input given to it and all interactivity with the visualization is limited to the visualization itself. The goal of this feature is to allow VisBuilder to allow visualizations to communicate back with VisBuilder about interactions happening in the visualization to perform actions.
Currently we use expressions that allow this form of communication via action handlers. We can use this mechanism to define certain action types (like API's) that a registered VisType can use to trigger actions in VisBuilder or app that it is embedded in.
Exit criteria:
Visualization should have a defined set of actions that it can emit
Actions should be well defined and cover most of the usecases already supported if not more
The text was updated successfully, but these errors were encountered:
Currently a visualization can only render information from the input given to it and all interactivity with the visualization is limited to the visualization itself. The goal of this feature is to allow VisBuilder to allow visualizations to communicate back with VisBuilder about interactions happening in the visualization to perform actions.
Currently we use expressions that allow this form of communication via action handlers. We can use this mechanism to define certain action types (like API's) that a registered VisType can use to trigger actions in VisBuilder or app that it is embedded in.
Exit criteria:
The text was updated successfully, but these errors were encountered: