Knowledge Base

Embedding reports within dashboards offers users convenient and quick access to the information they need. To further streamline working with such reports, the WEBCON BPS platform includes a feature that allows users to filter data directly from the dashboard level. This article explains and illustrates the functionality mentioned above using a selected business case.

Timers are elements that allow you to define the frequency with which the associated actions are performed. Thanks to them, it is possible to define the start time and the possible repetition cycle of such actions.
In WEBCON BPS 2025 R1, numerous changes and improvements have been made to the operation of Timers (previously known as Timeouts). This article describes these changes to the timer configuration and gives examples of how to calculate their start dates.

A new feature for hiding sensitive data that requires additional verification to access it.

The easy way to fix broken variables after formatting JavaScript code in VS Code.

A business rule to ensure the uniqueness of a field value

Implementing a Dynamics CRM style tab layout in WEBCON. For example, one group group on the left another one on the right and an third group beneath those two across the whole form.

While I have a lot feature's which I list und 'user experience' on my blog I was focusing on updating those for WEBCON BPS 2025: Breadcrumb, Colorize paths, Missing comment handler, Modal dialog, Uniform save experience

Microsoft Entra ID (formerly Azure Active Directory) enables secure identity management and control of access to cloud resources and on-premises applications. With the integration of WEBCON BPS with Entra ID, an effective and advanced identity and access management is possible in hybrid and cloud environments.
This article covers the installation of WEBCON BPS Standalone without a local Active Directory domain. Authentication and user list retrieval are implemented using Microsoft Entra ID.

This article explains how to integrate the WEBCON BPS platform with a SIEM service using the Microsoft Sentinel tool.

The OAuth2 authentication standard is becoming increasingly popular, as it enables integration between different systems. In many cases, the connection takes place in the API → Application model, which makes authentication much easier. In this case, a predefined set of data is used – Client ID, Client Secret, and our subsequent actions are authorized by the token received in return.
But what if it is crucial to determine the user's context? This need is answered by the OAuth2 Authentication form field, which allows the user to be authenticated before connecting to the API and performing operations. The scenario described herein presents this feature using communication between MS Graph and Microsoft Azure.