This Action targets a Stacked Visualization and brings a Visualization to the top of the stack so that it is visible.
Step 1: Add Action
Add the action as explained here.
Step 2: Base Config
| Property | Description |
|---|---|
| Action Name | Name that will be used in a context menu if more than one Action is configured for the event |
| Switch to Page | Allows an administrator to select a target Page for the Stacked Visualization. To update a Stacked Visualization on the current page, select the name of the current page. |
| Switch to Currently Displayed Visualization | Shows a list of Visualizations within a stack on the selected page. If multiple Stacked Visualizations exist on the Page, there will be multiple dropdowns. |
| Breadcrumb Strategy | Controls how the destination page name is added to the Breadcrumb. – Append: The default behavior — adds the destination page name to the end of the list. – Clear: Clears all entries in the breadcrumb and adds the destination page name at the root level. – Replace: Replaces the last entry in the breadcrumb with the destination page name. |
| Override Breadcrumb Strategy | Enabling this and selecting a field from the source page’s dataset will add the value of the field based on the row selected by the user to the destination page name in the breadcrumb trail. |
| Breadcrumb Label | When Override Breadcrumb Label is enabled, the administrator can inject some context-based label as well as other static text. Context value can be selected from record attributes from the source Visualization’s dataset. The administrator can also inject a page name. |
Step 3: Page Variables (Optional)
This is an optional step that allows you to set Page Variables on the target page in a couple of different ways. You can use:
| Option | Description |
|---|---|
| Record Value | Uses values from the record that is clicked by the end-user. |
| Page Variables | Uses values from the current Page Variables. |
Step 4: Conditions
This step lets you specify additional conditions that determine when an Action is fired. For example, suppose you are working with some event data, and only want to fire the Show Visualization Action when Totals < 1000. You add that logic here in the conditions step as shown in the screenshot:
Step 5: Permissions
Here you can exclude certain roles from accessing the action.
Example
