LMS-specific connectors

Prerequisites: the lms option on your account, without which the LMS sub-page does not appear. The CROSSKNOWLEDGE block additionally requires the crossknowledge-integration option, which is a separate one.

Only two platforms have a block of their own in the back-office: CrossKnowledge and WBT. The other LMS names you will meet in the interface are dropdown values, not connectors: the setting that matters is made elsewhere, with your support team.

Where it is set

Configuration › Integrations › LMS. The blocks follow in this order: LMS, CROSSKNOWLEDGE, WBT, LRS, then External content configuration.

In the LMS block, Setup default LMS opens the form that describes your account’s main configuration. Add other LMS opens the same form for an additional configuration; that button stays disabled until the default configuration has a Base URL. The additional configurations are then listed under Available Configurations.

The form itself asks for Name, Base URL, Authentication type (BASIC is the only value offered), Login, Password, Method name and User Id. Name, Base URL, Login and Password are required.

CrossKnowledge

The block is titled CROSSKNOWLEDGE, in capitals, in every interface language. It carries three settings: the Enabled / Disabled switch, then Base URL and API key, both hidden while the switch is on Disabled.

What those three settings turn on: every time a learner refreshes their capsule list, Beedeez re-reads their CrossKnowledge registrations and re-applies the resulting access. Two synchronisations for the same learner are separated by a minimum interval, fifteen minutes by default, which can be set to another value on your account. A change made on the CrossKnowledge side is therefore not visible straight away.

Once the switch is on Enabled, a Synchronisation tab appears on a learner’s record, under Statistics › Learners. Its Launch synchronisation button replays the synchronisation for that one learner and then states whether it finished or failed.

Nothing else. Publishing your capsules to CrossKnowledge as learning resources, sending tracking back, or identifying the learner at launch time all need information this block does not expose. Those three uses exist, but they are set outside the interface.

WBT

The block is titled WBT, not “WBT Manager”. One Base URL field, and two switches:

• Synchronize statistics on WBT manager using the API sends usage statistics to WBT through its API. It also makes a Synchronisation tab appear on a learner’s record, under Statistics › Learners. The button on that tab is labelled Force synchronisation and replays the synchronisation for that one learner, then lists the contents it processed.
• Auto import offline courses pours the offline courses the learner took on WBT into their Beedeez activity, on every refresh of their capsule list.

The block asks for no WBT administrator credentials. Launching a content from WBT needs them, so it cannot be set up from this screen.

TalentSoft

TalentSoft has no block of its own. It shows up in four places, all independent:

• in the LMS block, as a value of the Name field, where it only names a configuration ⚠️ see the trap below;
• in the External content configuration block, as a value of the Authentication field, not of the Resource field, which only offers REST. See Configuring an external content source;
• in the Scheduled jobs block, under Configuration › Integrations › Jobs & Reporting, as a value of the Source field on both external learning resource synchronisation jobs. See Importing an external training offer;
• as a family of reporting formats. It counts six variants, not five: activity, track actions, track sessions, track registrations, certifications, certification validations. See Ready-made reporting formats.

Say which of the four you mean when you raise the subject with support.

Cornerstone

In the back-office, CORNERSTONE exists only as a value of the Name field in the LMS block. The actual connection, which identifies the learner on Cornerstone at launch and then regenerates their access, is set entirely outside the interface.

A Cornerstone reporting format also exists. It is not selectable in the back-office either.

For content delivery, Beedeez produces nothing Cornerstone-specific: it is the ordinary SCORM export, described in Exporting a capsule or a track as SCORM and Automating SCORM delivery to an SFTP.

The trap

The Name field in the LMS block looks like a connector picker. It is not one. It offers eight values, WBT, CROSSKNOWLEDGE, CORNERSTONE, TALENTSOFT, SYFADIS, SUCCESSFACTORS, DOKEOS and MOODLE, and what it records is the name of the configuration. The connection is described by the other fields of the same form, starting with Base URL and the credentials. Choosing a name in this list does not, by itself, open a connector.

The interface half admits it: picking SYFADIS, SUCCESSFACTORS, DOKEOS or MOODLE shows the message “For this integration, please contact your support team who will help you to correctly configure the selected LMS.” The four other values deserve the same reflex.

What it does not do

• No connection test. Neither the CROSSKNOWLEDGE block, nor the WBT block, nor the LMS block’s form calls the remote platform on save. A wrong address only shows up on the first learner.
• No reporting format choice. The ready-made formats are exposed nowhere in the back-office, whatever the target platform.
• One Synchronisation tab only. The tab is the same one for both integrations. If WBT synchronisation and CrossKnowledge synchronisation are both active on the account, that tab shows the WBT button, and never the CrossKnowledge one.

Going further

• Setting up launch from your LMS: the mode that keeps the LMS as the entry point, with no specific connector.
• Configuring an external content source: the block where the TALENTSOFT value of the Authentication field lives.
• Ready-made reporting formats: what Beedeez can produce for Cornerstone, TalentSoft and the others.
• Configured with your support team: how to open the settings that are not in the interface.
• Sending xAPI statements to your LRS: the LRS block, next to the two above on the same sub-page.