Skip to content

Memory Hub

The Memory Hub is the catalog of the learner memory variables of your workspace. It also lists the stored keys that are not defined yet, and it generates JavaScript that saves values to memory or loads them back into your authoring tool. This page is for workspace owners and course authors.

Open it from the sidebar: Memory › Hub. Owners and Editors can open the Memory Hub; Viewers cannot.

A slide can save any key without defining it first. Such a key, sometimes called an ad hoc key, works in prompts like any other. Defining a variable in the Memory Hub adds these benefits:

  • it appears in the Learner memory group of the variable picker when you write instructions;
  • its description tells your team what the value holds and which slide captures it;
  • only defined variables can be used by the Memory Hub code to save or load values.

Only the workspace owner can change memory definitions.

  1. Click New variable.

  2. Fill in the New memory variable dialog:

    FieldWhat it doesExample
    NameThe name you see in SlideMind, on pills, chips and lists. Accents and spaces are fine; {, } and | are not. Each name can be used by one variable only.Learner first name
    VariableNot a field: SlideMind creates it from the name, for example memory.learner_first_name. It’s the placeholder used in prompts and the key under which values are stored. It no longer changes once the variable is added.memory.learner_first_name
    ScopeWhere the value is meant to live: global, course, module or slide.global
    Description (optional)What the value holds and where it comes from.Learner first name, captured on the intro slide
  3. Click Add variable.

Renaming a variable later changes only its Name. The Variable stays as it was created, “so prompts and stored values keep working.” The name also shows next to the key in Try it, the Sandbox and learner data.

The Memory Hub page with a catalog of five variables, their scope, the number of learners who have a value and the date a value was last stored

The catalog lists each variable in these columns:

ColumnWhat it shows
NameThe readable name, with the description below it.
VariableThe key, as used in prompts: memory.first_name.
ScopeThe scope chosen in the definition.
LearnersHow many learners have a stored value for this name at this scope.
Last storedThe date and time a value was last saved for this variable.

To change or remove a variable, the owner opens its ⋯ menu and chooses Edit or Delete. In the Edit memory variable dialog, Save changes stays inactive until you change something. Deleting removes the variable from the catalog only: “Values already stored for learners are not deleted.”

Below the catalog, the Keys found in memory, not in the Hub list shows the keys that hold learner values but match no catalog variable: “Captured by a slide but not defined here.” The list appears only when there is at least one such key. For each key, you see:

  • its name and where it is stored: Global, or the name of the course, module or slide, followed by its scope;
  • the number of learners with a value;
  • the date of the last activity.

Keys saved by exchange memory, such as conversation_rolePlayA, usually appear here. A key defined in the catalog at another scope also appears here, because its name and scope do not both match.

To use one of these keys with the Memory Hub code, the owner opens the ⋯ menu of its row and chooses Add to Memory Hub. The dialog proposes a name from the key, keeps the key as the variable and locks the scope to where the values are already stored. Add a description, then click Add variable. The key moves to the catalog, already ticked and ready to be loaded. The menu is not offered when the same name is already defined at another scope.

The Memory Hub generates two kinds of JavaScript. Neither belongs to a slide, and neither calls the AI.

ButtonWhat the code doesUse it for
Save to memoryReads authoring tool variables and saves them to the learner’s memory.Saving values from a screen that has no SlideMind slide.
Load into authoring toolReads values from the learner’s memory and writes them into authoring tool variables.Showing a saved value on screen, or branching on it, in Storyline or another tool.
  1. In the catalog, tick the variables, or tick the box in the header row to select them all. A bar appears below the catalog with the number of variables selected.
  2. In that bar, click Save to memory or Load into authoring tool (Load into tool on a narrow screen). Clear empties the selection.
  3. Choose the Authoring tool: Articulate Storyline, Adobe Captivate, Lectora, dominKnow | ONE or iSpring Suite.
  4. Under Memory → authoring-tool mapping, type the authoring tool variable for each memory variable. SlideMind proposes a name, for example FirstName for first_name.
  5. Click Copy code.
  6. In your authoring tool, create the variables with exactly the same names, then run the code in a JavaScript trigger or action. In Storyline, use an Execute JavaScript trigger.
  7. Publish the course and test it launched from your LMS.

The Load memory into the authoring tool dialog for Articulate Storyline, mapping memory.first_name and memory.profession to authoring tool variables

The code needs an identified learner: without one, it stops and saves or loads nothing. When the learner has no value for a variable, the load code leaves that authoring tool variable unchanged.

The Memory Hub code uses a single connection for the whole workspace, called the standalone memory bridge. The first time a workspace owner opens one of the two code dialogs, SlideMind prepares it automatically (“Preparing the standalone memory bridge before generating code…”), and Activity records Memory bridge generated.

Until an owner has done this once, an Editor sees: “A workspace owner must generate the standalone memory bridge before this code is available.” Ask the workspace owner to tick a variable and open Save to memory or Load into authoring tool once.

  • Global scope. The Save to memory code saves every value at the Global scope. The Load into authoring tool code reads only variables defined with the global scope: if one selected variable has another scope, the whole load is refused. Use Global variables with this code.
  • Defined variables only. Both codes accept only names defined in the catalog. A name that is not in the catalog is refused.
  • Allowed websites. The load code works only when Settings › Integrations › Allowed origins lists the site that hosts your course. An empty list, or the 24-hour CORS test mode, is not enough for loading. See Allowed websites.
  • Changes. The code contains the variable names and the authoring tool variables you mapped. After a change, generate and copy the code again.