Skip to main content
Version: 2024.1

BPS SDK

WEBCON BPS SDK is a set of libraries which make it possible to create plugins that allow complete customization of the WEBCON BPS system to meet all business needs. The extensions are run within the WEBCON BPS system, so they have to be implemented in Microsoft .NET Standard 2.0 technology, e.g. using the C# language. After registering within the system, they can be used in any process. The SDK infrastructure is an integrated part of WEBCON BPS and is available immediately after installation. You can use all plugins provided by WEBCON or partner companies. To develop and use your own plugins, you may need an additional SDK license (it depends on your type of installation and owned licenses).

SDK overview

Implementing a plugin consists of inheriting a class from an appropriate base class and then overriding relevant methods and finally including the logic of the plugin within them. Each plugin type has its own base class and a set of virtual methods as well as properties.

Plugins templates

The process of creating the SDK plugin is very simple. You can create your projects manually using Class Library, but you can also make use of provided templates that make this operation even more effortless.

Types of plugins with examples of use cases

Custom actions

  • Validation
  • Communicating with external system
  • Changing form field values
  • Generating custom signature
  • Assigning tasks

Custom business rules

  • Validation
  • Implementing complicated logic and calculations
  • Changing form appearance
  • Changing form behavior

Custom data sources

  • Loading data from external sources that can’t be handled by built-in data providers

Custom label printing templates

  • Creating custom label (stickers for marking documents) appearance
  • Handling printouts by an external system

Resources

Examples of SDK plugins are available on our GitHub, full list is available here.
The My first SDK action section provides a series of articles guiding you step by step through the process of creating an SDK Action.