Jump to Content Item

The Jump to Content Item jump action opens another content item (either a discovery or a presentation) when the jump button is clicked. You'll need to select which content item to open, and the method to use to open it (in a new tab or a pop up, for instance).

Configure a Jump to Content Item Action

From the Jump Actions panel, choose the action type, the content item to open, and the method by which to open it.

Choose Action Type

From the Choose Action Type drop-down list, select Jump to Content Item.

Jump to Content Item

Under Jump to Content Item, find and select the required data discovery or presentation from the Content tree (red highlight above). Once selected, you can click the Open Item button (green arrow above) to open it in a new tab.

Open In

From this drop-down list, select where you want to the content item to open:

• New Tab: when the jump button is clicked the content item will open in a new tab.
• Pop Up: when the jump button is clicked the content item will open in a pop up.
• Pop Up with iFrame: when the jump button is clicked the content item will open in a pop up inside an iFrame. This will give the user access to the Present runtime menu and Panels within the pop up.
• In Place: when the jump button is clicked, the user will navigate away from the presentation to the content item in the current browser tab.

When ready, click Apply to save the jump action.

Ignore Cross-Model Mappings

When the selected action type is Jump to Content Item, any interactions at runtime are applied to the content item opened by the action. By default, Pyramid recognizes any cross-model mappings that have been configured between items with interactions, but you can select Ignore Cross-Model mappings on the Actions Settings tab to ignore any cross-model mappings and instead produce an error.

Note: Cross-model interactions enable interactivity between content items from different data sources. These interactions are only supported "out-of-the-box" between models with the same structure. If you add interactions between items whose models have different structures (for example, different data types, formatting, hierarchies, and so on), the interactions will fail at runtime unless a Model Mapping is defined that maps the items in one model to items in the other. For more information, see Model Mapping in Present Pro.

Example