Rules, JS, SQL

Artificial Intelligence (AI) plays an increasingly important role in automating and streamlining business processes. Today's organizations are seeking to increase efficiency by implementing solutions that enable intelligent information processing. WEBCON BPS, as a platform that supports business process management, is constantly developing its capabilities in this area. The latest version, 2025 R2, introduced a number of AI functionalities that help users to analyze text, process recordings and interact with language models. This article describes these functionalities and provides examples of how to use them.

Not all characters we can use in WEBCON for attachments are supported by SharePoint.

Have you ever needed to trigger an action after uploading or modifying a document? I’m not sure about you, but we recently faced this exact challenge. After some quick research, we came up with a relatively simple JavaScript function that triggers a 'Save' button click when an attachment is added or modified. Of course, the function can be adjusted according to specific needs.

How to use the min/max and step attributes for numeric inputs to limit the input to a certain range.

There are to many attachments when displaying "All attachments"? Display them collapsed on form load.

This article shows, how we can easily configure the open file dialogue to only show certain file types

What are the differences between a "save" path and the save menu action? How can we have always a menu action and a save path button?

This post provides a solution to extracting the latest comments in the standard "Comment" field on the form.

This article describes the rules for configuring Task delegation substitutions, taking into account user privileges in the context of multiple databases, as well as the roles of WEBCON BPS Workflow Service and global system settings.

Form rules, as the name suggests, are rules that define the behavior and appearance of form elements. When working with form rules, there may be a situation where execution of one function or subrule interrupts execution of the entire rule. Consequently, the rest of the rule is not executed. This article provides a detailed description of the reasons for this behavior and a proposal for creating rules so that they work as intended by their author.