Difference between revisions of "ATC/Current/SDK/Load modules"
From Genesys Documentation
m (Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2") |
m (Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2") |
||
| Line 6: | Line 6: | ||
|Dimension=Modules | |Dimension=Modules | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage-onpremises, PureConnect, | + | |Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud |
|Prereq= | |Prereq= | ||
|Section={{Section | |Section={{Section | ||
Revision as of 11:59, July 15, 2020
This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.
Learn how to add the functionality of a module to to the Journey JavaScript SDK.
Description
Use the load function to load modules. When you load a module, its functionality is immediately added to the Journey JavaScript SDK.
Signature
ac('load', moduleName, ,[userOptions], [callback])
Arguments
moduleName
- Description: name of the module to load. The module must be on the list of valid modules.
- Type: string
- Status: required
userOptions
- Description: configuration for the loaded module
- Type: object
- Status: module dependent
- Properties: module dependent
callback
- Description: callback that triggers when the module has finished loading
- Type: function
- Status: optional (default implementation does nothing)
- Arguments
- On failure, load passes an error (like InvalidModuleError)
- In other cases, load passes module-dependent values to the callback
Example
Comments or questions about this documentation? Contact us for support!