The UserContext used for this SDK.
The datasource connection used by this SDK.
Private singleton instance of this SDK. There should always be only 1 instance.
getter method for namespace. Provides the salesforce org namespace
setter method for namespace. Set custom namespace
Create a default GetAssetByAccountInput object.
Create a default GetAssetInput object.
Create a default GetContractInput object.
Create a default GetOfferInput object.
Returns offer.
Returns offer.
Returns a list of contracts.
Returns offers.
Returns the response after successful api call.
Invoke an action returning from previous API call.
Method to parse asset response
Returns the version number of SDK.
Returns SDK version number as string
Create a AccountSDKConfig object that consists of a UserContext and a DataSourceService for login user.
Configuration object to instantiate SDK.
Adds all the enumerable string keyed function properties of a source
object to the sdk prototype.
.extend
should only be used to add new methods and it won't override the existing methods.
Note: If the property already exists, it will be not be added.
Custom functions which are being extended should have proper namespaces to avoid issues during upgrades. When Vlocity releases new changes it won't impact if unique namespaces are used.
Example: myCompanyOrFeatureMethodName
The object of functions
Adds all the enumerable string keyed function properties of a source object to the sdk prototype.
.override
method should only be used to override the existing methods and should only be used in rare cases.
Overriding the existing or default methods may cause unintended consequences and may also impact during upgrades.
Please be cautious while using this
The object of functions
Generated using TypeDoc
Account SDK Facade to to access account related information.
The Account SDK is a JavaScript library that abstracts and simplifies the use of API REST calls.
The SDK provides error checking and validates parameters before submitting them to the APIs, ensuring that calls to the APIs are well formatted and complete. In some cases, the SDK invokes more than one API to complete a request.
Using the SDK ensures that errors are detected before API calls are made, ensuring that Vlocity data structure rules are enforced and that data is not written incorrectly to the Vlocity cart or to the product database.Using the SDK reduces UI development efforts by consolidating common application and business logic to use the Account APIs.
SDK components can be shared by different user interfaces, such as: Customer custom UI Components (which can be based on any framework), CMT Mobile App Shopping UI, Omniscript that uses Account APIs, and so on.
v109.0.0