Introduction
Docebo Flow allows you to start an instance of your Docebo platform on any external web page, as long as you have access to its HTML and JavaScript code.
The Docebo platform instance opens as a pop-up activated either when the user clicks on a button or interacts with an element - such as a link, or a string - on the external web page. When the pop-up opens, the platform instance shows the training content you, as the Superadmin, have selected for the user on the basis of the action he or she is performing, in order to provide the best learning on the fly experience, enriching it with ad hoc training.
Depending on the Docebo Flow configuration, users can be automatically provisioned so that their learning on the flow of work is not an event interrupted by the need to log in.
Docebo Flow is available as a web-based application on desktop and mobile platforms.
The Docebo Flow Launcher allows you to open an instance of your Docebo platform in any external web platform, as long as you have access to its HTML and JavaScript code. Find out more on Docebo Flow and the Docebo Flow Launcher in their respective knowledge base articles.
This article is a technical guide on how to interact with the Docebo Flow Launcher using commands in your web platform.
Lifecycle commands
Command | Description |
---|---|
setTokenProvider(callback) |
Provides the launcher a function to invoke when the current access token expires. The provided function must return a Promise that resolves with the new access token. This command uses the following parameter:
Example: function renewToken(){ |
start({ |
This command starts the app launcher. This command uses the following parameters:
The command returns a promise that resolves when the app launcher has fully started and loaded. This makes the parent page to become aware of the status of the launcher which allows for the triggering of events based on that information. The start command promise resolves only after the launcher is ready to be shown. This gives you the ability to use this feature to open the launcher automatically or, for example, perform searches behind the scenes prior to displaying the results. Example: DFlow.start({ By default when the app launcher is first started, it will display the icon only with the popup in a closed state (see the Interaction commands section; the default state after (In case of Custom Button usage the opening the logic remains the same but the Icon will not be shown) Please note: An older version of this command, which does not have the ability to set the language parameter, can also be used to start the launcher. |
shutdown()
|
This command stops and removes the app launcher from the screen. Returns a promise that resolves when the app launcher has been terminated. Example: DFlow.shutdown() |
restart({ |
This command restarts the app launcher. This command uses the following parameters:
Returns a promise that resolves when the app launcher has fully started again. Example: DFlow.restart({ Please note: An older version of this command, which does not have the ability to set the language parameter, can also be used to restart the launcher. |
Interaction commands
The following commands allow the user to interact with the launcher on the page. The command structure is set out as follows:
DFlow.getCommandBus().send(
'action',
'widget ID',
{}
)
Please note that the widget ID is always “launcher”. These commands do not return a response promise payload.
Command | Description |
---|---|
DFlow.getCommandBus().send( |
This command makes the launcher visible if it has been previously hidden. |
DFlow.getCommandBus().send( |
This command hides the launcher. |
DFlow.getCommandBus().send( |
This command opens the launcher container. |
DFlow.getCommandBus().send( |
This command closes the launcher container. |
DFlow.getCommandBus().send( |
This command toggles the launcher container open status. |