search results

Applies to version: 2022.1.x and above; author: Jacek Język From WEBCON BPS 2022.1.1, the lowest supported SQL Server is 2014. In the case of WEBCON BPS installations using the higher versions of SQL Server, WEBCON BPS databases work with the compatibility level set to SQL Server 2014 by default. Changing the compatibility level from SQL Server 2014 to SQL Server 2019 is possible, but

Starting with WEBCON BPS 2022.1.1, the lowest supported MS SQL Server version is 2014. Due to this, when installing WEBCON BPS, the Compatibility Level for databases is set to 120 – which corresponds to SQL Server 2014. This setting is also used when installing WEBCON BPS with newer versions of SQL Server (2016, 2019…). However, please note that when updating the WEBCON BPS platfo

  Applies to version: 2021.x.x.xxx and above; author: Mateusz Syrek Introduction This article describes 3 variants for transferring WEBCON BPS databases to a different SQL server: new server has the same name as the old one, new server has a different name – applying SQL aliases, new server has a different name – no SQL aliases applied, changing configuration

Applies to version: 2022.1.3 and above; author: Maciej Kieblesz   Introduction This article describes a method of maintaining databases to ensure the highest possible performance of the SQL engine, and thus the BPS application itself. In practice, this will mean a reduction in the number of 'timeout' errors, for example, when loading a report. This mechanism is tailored to

Applies to version 2019.1.x; Author: Przemysław Sierant Introduction WEBCON BPS 2022 introduces a new version of the mobile application. One of the changes made is the process of creation of the user profile. It is still possible for the system administrator to prepare a BPSX file in order to send it to a specific user as it was done so far. Specific configuration can be found h

Applies to version: 2022.1.x and above; author: Łukasz Maciaszkiewicz   Introduction Increasing data volumes combined with shrinking disk space and decreased performance pose a challenge to every IT system. WEBCON BPS faces it with an extensive archiving mechanism that automatically removes data from process databases. The resulting better arrangement of disk space translates into e

Applies to version: 2022.1.x and above; author: Krystyna Gawryał   Introduction Outlook Classic is an add-in that allows WEBCON BPS to integrate with the Outlook desktop application available as part of Microsoft Office, which is one of the most widely used applications for managing e-mail correspondence in enterprises. Upgrading it with a dedicated WEBCON add-in will allow users to e

Applies to all versions; Single-Use Access licenses available from 2023.1.1 and above. Licensing models WEBCON BPS is currently available in two licensing models – as a subscription or perpetual license paired with an annual Software Assurance payment (which allows updating to newer versions). Perpetual licensing is not usually offered on most modern markets, except for obta

Applies to version: 2023.1.x and above; authors: Marcin Kapusta, Krystyna Gawryał   Introduction The newly released version of WEBCON BPS (2023.1.x) enables containerization of the system components. Thanks to this, it possible to use Docker images provided for WEBCON BPS Portal, BPS Workflow Service, and Search Server (Solr) and run these modules in containers. Containerization

Applies to version: 2023 R1 and above; author: Łukasz Maciaszkiewicz   Introduction The logic behind the execution of tasks by service is a multi-faceted and complex issue. When planning tasks, application designers are often unaware of the mechanisms and rules used by the service. To fill this gap, this article describes the elements affecting the sequence in which the service exec

Applies to version: 2023 R1 and above; author: Łukasz Maciaszkiewicz   Introduction In the present-day dynamic and distributed application environments data monitoring and analysis are key to ensure high efficiency, reliability, and optimization of an application. To address those challenges, the 2023 R1 WEBCON BPS version has introduced support for OpenTelemetry – a powerful

Applies to version: 2023.1.x and above; author: Marcin Smarzewski   Deactivating Licenses on Test and Developer environments Before mirroring the environment, it is recommended to deactivate the test or development license service (depending on which environment will receive the production mirror), Doing so will make it possible to activate the license service without assistance. If

Applies to version: 2023.1.x and above; author: Michał Bednarz   Introduction The feature to install WEBCON BPS modules in containers was added in version 2023 and has been described here. Now that the platform can be run based on container services, we can employ various modern services like Kubernetes to launch and manage our application.   Requirements W

Applies to version: 2024.1 and above; author: Marcin Kapusta    Introduction In WEBCON BPS 2024 R1, the Search Server component uses a new version of the Apache Solr index to search for data – 9.6.0. Because of this, updating WEBCON BPS will require additional steps. Most of these steps will be carried out automatically by the installer, nonetheless, some will need to b

(...) nt mirroring procedure is described in the article Mirroring environments (for 2023 Standalone). ​​​​​​​ ​​​​​​​4.4 Extended environment If WEBCON BPS components are installed on more than one application server (HA/failover scenarios), the upgrade must be performed on each machine, as all components must run on the same, newer version of the platform. The step "3.6 Component installation" will (...)

(...) the components from working correctly and will require configuration changes to the environment. This article lists the steps that must be taken to ensure that the system works correctly when the application server needs to be renamed. In the examples shown in this article, the machine name has been changed from “WINSRV2022APP01” to “WEBCON01”.   1. Deactivate the license s (...)

(...) Fig. 1. Diagram showing the communication between Public Forms and WEBCON BPS   For security reasons we recommend to install Public Forms on a different machine than the one where the BPS application server is installed.   Installation First, download Public Forms from the official GitHub account, available at: WEBCON bps GitHub. On the main page you will find the source code, which you ca (...)

Hello! Is there anyone who could help me figure out how to call an external REST API from behind a corporate proxy? I manage to successfully call it using Postman application installed on the server where Webcon is installed. However, when the same call is made from Webcon, it doesn't work. I'm using the POST method of the "Invoke REST Web service" action on a menu button. If I enable "Use proxy"

Does anyone know if it's possible to show data not present in an application on the report? I have read the article about calculated columns (https://community.webcon.com/posts/post/using-calculated-columns/196/3) but that's not my case. What I would like to do is join the items from the report to a table in a different database (on the same server) or to an existing MSSQL data source. In many p

Dear Community, we have installed WEBCON BPS Standalone and published it through Azure AD Application Proxy. We are synchronising users in BPS with on-premises Active Directory. Currently we experience timeout issues after some time of inactivity on WEBCON BPS site. Sometimes it's few minutes, sometimes about 1 hour. See example in attachments. Please notice that WEBCON BPS and SQL Server (VMs) a