Depending on the functionality that you are implementing, it may be necessary to expose some administrative options within the Administration UI of Verint Community. The Administration UI is completely…
The platform allows developers to extend the content editor to provide for richer content.
Why Extend the Content Editor?
The content editor allows the input of html, images and video, however other…
Depending on the functionality that you are implementing, it may be necessary to expose contextual management options within the front UI of Verint Community. In other words, if you want to add custom…
Factory default widget providers allow for a logical and physical separation of widgets .
Why use Factory Default Providers?
Source Control. Each factory provider has a separate folder where its…
HtmlHeaderExtensions allow a plugin to insert additional headers into response. It does not allow overwriting or editing the existing tags in HTML header.
Creating an HtmlHeaderExtension
To create…
HttpCallbacks allow plugins to respond directly to HTTP requests.
Why use an HttpCallback?
HttpCallbacks are a platform supported alternative to HttpHandlers. Additionally the platform validates…
Custom functionality may require that URLs be defined that can be referenced by code to enable specific workflows (editing content, viewing content, listing content, etc). New pages can be declared in…
The Socket Framework provides support for real-time two-way communication between Verint Community and the browser . This enables receiving and sending messages directly to specific users or scoped groups…
When developing custom extensions using plugins , it is often beneficial to install UI components as part of the installation of the extension making use of the IInstallallablePlugin interface and the…
Widgets define the context they require to render. For example, the Blog - Post widget always displays the current contextual blog post. It is dependent on having a blog post available to render. The Blog…
