Applies to versions: 2024 R1 and above; authors: Łukasz Chechelski, Jacek Język Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Users and groups synchronization | WEBCON BPS Authentication providers | WEBCON BPS Introduction Microsof
(...) h configured access authorization in certain areas is not possible. These include: Reports – chart and calendar views Dashboards – fields are not available in the configuration of data source s (or any place that uses these data source s, such as filters or tiles), Compact view – distinguishers set up in the process configuration. Form fields with access authorization (...)
(...) lustrates the functionality mentioned above using a selected business case. Reports on dashboards Adding a report to the dashboard involves embedding its widget and linking it to the data source associated with that dashboard. This functionality enables convenient management of data source s directly from the dashboard and allows multiple reports to draw data from even a single source. This s (...)
Applies to version: 2024 R1 and above; author: Łukasz Chechelski Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON Help: Integrations Introduction The Public Forms mechanism is an interesting solution that allows you to create external forms whose
Applies to version 2025 R1 and above, author: Krystyna Gawryał Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Workflow designer | WEBCON BPS Global form template | WEBCON BPS Field matrix | WEBCON BPS Form | WEBCON BPS Introduction
Applies to version: 2025 R2 and above; author: Krystyna Gawryał Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Business rules | WEBCON BPS AI Create transcription | WEBCON BPS AI Implementation Guide AI Agent AI Concierge Other relate
(...) BCON BPS starts with defining the basic information: name, description, and mode of operation. We can decide whether the API should enable the triggering of automation, retrieve data from an existing data source or perhaps return information about a specific workflow instance. Depending on the selected mode, the rest of the configuration will be slightly different. In the case of automation, we create a s (...)
Applies to version: 2025 R2 and above; author: Kacper Świętek, Lily Adamowicz Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Sign an attachment Verify attachment’s signature The entry is an extension to the article Signing document with Au
(...) dash; particularly entries located deep within the structure. A typical example of data that benefits from tree-based presentation is a company's organizational structure. Changes to data source configuration (since version 2019) Earlier versions of the system supported a different approach to configuring the data source for the Choice tree form field (as described in the article Atrybut (...)
(...) invoice content, analyze it according to the instructions, and return the result as a JSON object. The resulting JSON is then stored in the technical field "_invoice data", serving as a data source for further processing. The query inserted into the AI PROMPT function in the TEXT field is shown in the screenshot below: At this stage, the data is not yet visible (...)
(...) content database, causing them to stop working. Therefore, they must be updated by changing the address, name, and/or credentials of the account used for the connections. If SQL queries (data source s, Run an SQL procedure actions, business rules containing the SQL COMMAND function) include explicitly defined database names, these must also be updated if they have changed. &nb (...)
(...) lysis endpoint. First you have to set up once the necessary Entra application registration and the WEBCON MSSQL database connection to the lakehouse SQL analysis endpoint. Then you can create as many data source s in WEBCON Designer Studio as you wish to query your tables in the lakehouse. Microsoft Entra App As you need a service principal for your MSSQL connection you have to create a new Entra app (...)
(...) in Designer Studio. Solution Solution is rather simple - instead of creating a Fixed Values List, we will create a group of constants like this one: On top of that, we'll add new SQL data source with query getting all constants inside of our Group (we need to get the GUID of the group too, and i'll come back to this in a second). SELECT epv_default AS id, epv_guid AS guid, epv (...)
(...) you would like to enter the values on the fly. In my latest post I talked about how to simplify this approach using a centralized source and a decentralized variation: The centralized data source has a backing dictionary which is used to store and manage the data. The decentralized data source has no backing dictionary. You can simply select a value from already existing ones or add a new o (...)
The idea behind this proof of concept is to find a way to use a picture field to enter information such as errors, defects, deviations, or - since we are a construction company - pipe or cable routes. I already had this idea back in 2022. My solution is to use the signature field as a drawing board and then copy the result back into a picture field. Perhaps this will also serve as a sta
Applies to version: 2026 R1 and above; author: Lily Adamowicz. Adrian Baszak Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON Help: AI Agent AI Implementation Guide Other related Community articles include: AI Agent analytics
(...) nical blog. After adding the OAuth2 Authentication field to the form, the next step is its configuration. To do this, go to the OAuth2 connections configuration in WEBCON Designer Studio. Under data source s → Authentications → OAuth2 User -> API, create a new authentication that will be used to confirm the user’s identity against the Microsoft Graph API. Configure it as follows: & (...)
(...) ibed (this also applies to the field I want this tooltip for users, the content of which is then presented in the form of a tooltip on the form). For most Picker fields, the AI Assistant also creates data source s. For example, in the case described, the AI Assistant created the data source s “Currency”, “Invoice Status” and “Invoice Type” for the corresponding Dropdown choi (...)
Applies to version: 2026 R1 and above; author: Adrian Baszak, Lily Adamowicz Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON Help: AI Agent AI Implementation Guide Other related Community articles include: AI Agents – Business
(...) n the address bar. The Grafana tool log-in website is displayed. The default user name and password is “admin” (you can change the password after logging in). Add a data source to enable the tool to visualize and monitor data. To do that click the data source tile located in the tool’s main window. Select the Prometheus option from the list of availab (...)