Verint | Telligent Community
Verint | Telligent Community
  • Site
  • User
  • Site
  • Search
  • User
Verint Community 13.x
  • Verint Community
Verint Community 13.x
Developer Training Getting Started
  • User Documentation
  • Ask the Community
  • API Documentation
  • Manager Training
  • Developer Training
  • Tags
  • More
  • Cancel
  • New
  • Getting Started
  • +External Integration
  • +Plugins/Framework extension
  • +Automations
  • +UI Customization
  • +Notifications and Email
  • +Scripting
  • Obsolescence

Getting Started

The Verint Community platform is developed to enable you to build your own customized community. Beyond the options exposed to configure, layout, and customize a Verint Community-based site using options exposed through the UI for end-users, the platform provides many opportunities to extend and use the platform via custom development as well.

Extensibility Architecture

The architecture of the platform with respect to extensibility and custom development opportunities is outlined below:

With the goal to provide community functionality to your end users, Verint Community provides multiple paths:

  1. UI Customization via UI Extensions, Themes, and Widgets
  2. Automations
  3. Integrated Applications / Plugins
  4. External Applications

UI Customization via UI Extensions, Themes, Widgets, and Embeddables 

The Verint Community primary user experience is delivered through the platform's end-user customizable theming engine that enables drag-and-drop functionality selection, layout options, configuration, and customization using widgets to form web-based experiences. User generated content can make use of embeddables which implement specific formats or functionality within content.

The default experience can be heavily configured through the platform's management features and extended through specific extensibility points. To get started with customizing the UI, see UI Customization.

Automations 

Automations are scripted extensions to Verint Community that can be used to implement business rules and extend the functionality of the platform by handling platform events, running as a background process on a schedule, or being accessible as custom HTTP endpoints. Automations can also provide reusable custom APIs to widgets, themes or other automations.

To get started with implement custom business logic, see Automations.

Integrated Applications / Plugins 

Verint Community enables Microsoft .net developers to integrate with the platform by developing plugins that register directly with the core web and job server implementations for tight and direct integrations and extensions.

All of the core platform functionality (groups, applications, video rendering, API exposure, etc) are built using this plugin architecture. Integrations using plugins are first class citizens in the platform.

To learn more about developing plugin-based integrated applications, see Plugins/Framework extension.

External Applications 

Verint Community enables community exposure limited only by your imagination. Community functionality can be exposed in other web sites and applications and community automation can be implemented via external integrations making use of the REST API and web hooks.

To learn more about integrating with external applications, see External Integration.

The Content Model 

The Verint Community platform provides global social interactions against an abstracted and extensible content model. This model is used regardless of the entry point used for customization or extensibility and is a core concept to development on Verint Community.

  • Created over 1 year ago
Was this helpful?
  • Yes
  • No
  • More
  • Cancel
Recently Updated Articles
  • Article
    Adding Scopes to Custom REST Endpoints
    Custom REST Scopes If you have created custom REST endpoints then as of 12.1 you should also be creating custom scopes for those endpoints. Otherwise they appear as uncategorized and controlling access becomes more of a challenge. To create scopes…
  • Article
    REST Authorization using PKCE (Proof Key Code Exchange)
    PKCE, or Proof Key Code Exchange, is an extension of the authorization code flow in OAuth 2.0 that solves the "public" client issue. Public OAuth clients, or clients that cannot reliably or practically protect a client secret will generally use the Implicit…
  • Article
    REST Scopes
    Custom REST Scopes If you have created custom REST endpoints then as of 12.1 you should also be creating custom scopes for those endpoints. Otherwise they appear as uncategorized and controlling access becomes more of a challenge. To create scopes…
  • Article
    Single Sign-On Plugins
    Custom Single Sign-On Providers Single Sign-On providers are plugins that facilitate authentication using an identity provider. This means user information and credentials are stored in a third party application and the community will delegate the responsibility…
  • Article
    Authentication
    All REST requests must be authorized to access the REST API. When accessing the REST API from javascript in a widget through the $.telligent.evolution REST methods, no additional headers must be specified. For all other scenarios, REST headers must be…
Most Helpful Articles
  • Article
    Factory Default Widget Providers
    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 widgets are stored (in the filestorage folder under…
  • Article
    Customizing the Rendering of Individual Configuration Options
    Many plugin types support exposing configuration options (for example, IConfigurablePlugin ). Configuration options can make use of shared property templates that cover many configuration needs. If a plugin exposing configuration needs a custom rendering…
  • Article
    Interacting With Files
    The Verint Community platform provides support for creating file stores within the Centralized File Storage System to enable plugins to store, secure, serve, and generate files. Why Would I Create a File Store? A file store is a unique set of paths…
  • Article
    UI Automation
    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 UI automation API. What is the UI Automation API…
  • Article
    Using Theme Palettes
    Theme palettes allow themes to expose sets of configuration options to theme managers to make groups of configuration easier. The theme, widgets, and other scripted customizations can expose options to select a palette from the current theme and retrieve…
  • Telligent
  • Professional Services
  • Submit a Support Ticket
  • Become a Partner
  • Request a Demo
  • Contact Us

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community