Conversation
|
Later on the actions will also be added to other widget types. The next one in turn is the graph and map vizualizations. The examples in the doc's now is for table action. Should we mention / structure the docs so the examples states what chart type they are for? |
jehellqvist
left a comment
jehellqvist
left a comment
There was a problem hiding this comment.
Nice to see the docs coming together, left some comments on the different parts.
There was a problem hiding this comment.
This screenshot will need to be updated, the icon with the "set parameter and navigate to" should have been deployed.
| * *Set parameter*: Send a value to a parameter, which can update the rest of the dashboard so visualizations respond to the selection. | ||
| * *Navigate*: On click navigate to an external URL, a Bloom scene, another dashboard. | ||
| Or a specific dashboard page within the same dashboard, optionally passing a parameter into that dashboard page's visualizations too, creating a drill-down into another page (the following example demonstrates this). |
There was a problem hiding this comment.
I think this section can be a bit more clear. Can the navigation action be divided into two navigate bullets? Since navigate actions will also set a parameter we could include that info under the navigate bullets.
Something like:
Set parameter: Send a value to a parameter, which can update the rest of the dashboard so visualizations respond to the selection
Navigate to dashboard page: Opens a specific page within the current dashboard. This is typically used to create a "drill-down" effect, where the Set Parameter action filters the visualizations on the destination page (the following example demonstrates this).
Navigate to external URL: Directs the user to an external URL. The Set parameter value can be embedded directly into the URL string to pass the parameter value to the external target.
Note: A navigation action cannot be configured without also defining a parameter value to be set.
| An action is event-driven. | ||
| When a value is clicked an *action* sets it as a parameter value. | ||
| Any card with a Cypher query that includes that parameter responds immediately, so visualizations update dynamically based on the selection. |
There was a problem hiding this comment.
Since the action can be configured to assign any table row value to the parameter I think we need to update this part. Maybe something like:
| An action is event-driven. | |
| When a value is clicked an *action* sets it as a parameter value. | |
| Any card with a Cypher query that includes that parameter responds immediately, so visualizations update dynamically based on the selection. | |
| An action is event-driven. | |
| When an action trigger within a visualization is clicked, it assigns a value to a parameter. | |
| Any card with a Cypher query that includes that parameter responds immediately, so visualizations update dynamically based on the selection. |
There was a problem hiding this comment.
| An action is event-driven. | |
| When a value is clicked an *action* sets it as a parameter value. | |
| Any card with a Cypher query that includes that parameter responds immediately, so visualizations update dynamically based on the selection. | |
| An action is event-driven. | |
| When an action icon within a visualization is clicked, it assigns a value to a parameter. | |
| Any card with a Cypher query that includes that parameter responds immediately, so visualizations update dynamically based on the selection. |
| @@ -0,0 +1,92 @@ | |||
| = Report actions | |||
There was a problem hiding this comment.
We changed the naming "Report actions" in the UI to only "Action" because we don't really have the concept of reports in dashboard. Can the page be called only Actions? Or maybe Widget actions? Maybe @nielsdejong have input on this?
|
This PR includes documentation updates New pages: |
3 participants
No description provided.