Canvas Guides (English)ImpactImpact Guide Blackboard Learn Ultra ExperienceHow do Impact contexts work differently in the Blackboard Learn Ultra Experience?

How do Impact contexts work differently in the Blackboard Learn Ultra Experience?

Blackboard Learn Ultra has a unique integration framework that presents some differences in the way Impact content, contexts, and monitors are experienced. Because the Blackboard Learn Ultra Experience is a locked-down system from Blackboard, Impact Building Block can’t be loaded in an Ultra environment. Due to this limitation, Impact has a slightly different integration compared to other LMS environments. If your LMS is the Blackboard Learn Ultra Experience, there are several differences in how you will experience Impact messages, support, and contexts. This article explains the key differences in context use within Ultra environments and how Impact has created a new framework to prevent any unwanted behavior with contexts.

Please read How do I install the Impact integration in the Blackboard Learn Ultra Experience? to ensure you have the proper setup.

You will also need to download the Impact Expert Tool plug-in from Google Chrome to activate the inline editor in your Ultra environment.

Please read this article for instructions on how to download the plug-in.

How does Impact work with the Blackboard Learn Ultra Experience?

Due to the closed integration system which prevents the Impact Building Block from loading, Ultra does not let you scan pages for elements with the Impact inline editor. This changes the process of defining contexts.

To prevent the majority of limitations, Impact has collaborated with Blackboard to develop a framework for Ultra users, called the Ultra Extension Framework. There are several differences in this framework compared to other LMS environment frameworks. These differences are explained below.

Blackboard Learn Ultra Experience Page Definition

In the Blackboard Learn Ultra Experience, users are not able to use the free select mode to select page elements. The way Ultra is set up limits the amount of unique information Impact can use to classify pages and page elements. For example, a test button and an assignment button on an assessment page could appear the same to Impact due to the unique way Ultra Pages are defined with Route IDs and Analytics IDs.

Route IDs and Analytics IDs

Route IDs and Analytics IDs

The Ultra Extension Framework enables Impact to see pages and page elements within Ultra. These pages and page elements are defined with Route ID’s and Analytics IDs.

Route IDs

In Blackboard, every page has a Route ID. Route IDs include some hints regarding the navigation paths of certain pages. These Route ID’s change depending on the user's navigation path through Ultra (i.e., you can enter pages from different locations, and these different paths can be recorded in the Route ID).

Analytics IDs

Page elements are not referred to by names such as buttons and links. Instead, they have Analytics IDs. Analytics IDs can be but don’t have to be unique, creating some confusion for users who want to go in and identify certain elements to attach Impact content, context or monitors to.

How does Impact help?

Having identical or hard-to-determine pages and page elements can create confusion when creating contexts manually. For this reason, Impact has defined all of the pages in Ultra as out-of-the-box pages using partial Route IDs to avoid any incorrect behavior or limitations that could occur with very specific Route IDs. This is also why your Define button is hidden when you use your inline editor unless you are on an LTI page.

The partial Route ID that Impact uses to define pages out-of-the-box is the part of the Route ID that all navigation variations have. (No matter where the user comes from in the LMS their route will contain the partial Route ID). By only taking the partial Route ID, Impact is helping you avoid any over-specifications in the navigation that could lead to limited usage reporting and functionality.

LTI pages are the only pages on which the Define button is visible and when you can actually define a context manually. To learn how to define LTI pages in Ultra, please read this article.

If you find a page in your Ultra LMS that isn’t defined (including any LTI pages if you don’t want to define it yourself), please submit a ticket.