search results

(...) h form rules. By default, the configuration of such rules is inherited from the settings of the main form, but, similar to the first case, it is also possible to break the settings inheritance; Security level (System settings → Global parameters → Required mobile application Security level). This setting is common for all WEBCON BPS applications and processes. It requires the user (...)

(...) sage context is not lost if images do not display. Be cautious with background images as support for them is not universal. 7. Avoid JavaScript: Most email clients do not support JavaScript due to Security reasons, so relying on any scripts to modify your email dynamically will likely not work as intended. 8. Character Encoding: Always specify a character set in your HTML emails. Using <meta char (...)

  Applies to version: 2023 R3 and above; author: Łukasz Maciaszkiewicz   Introduction With the release of the 14th cumulative update (CU14) for Microsoft Exchange Server 2019, there has been a revision in the approach to the Extended Protection feature. As a result, the feature, previously optional in earlier update packages, is now automatically enabled by default during in

(...) e of one of its cells. This value originally defines the row and makes it unique, even if the values of other cells of this row overlap with the values of analogous columns of the Item list. A Social Security number (SSN), Tax Identification number (TIN), identification card number, school/student identification card number, product serial number/code, Vehicle Identification Number (VIN), vehicle registra (...)

(...) contains Java. It is a required prerequisite on the operating system where Search Server will be installed. Such an approach allows the admin to update Java to the newest version (e.g. because of Security updates) without needing to update WEBCON BPS. Carried out by: environment admin   Step II – Backup copy of user activities During the Apache Solr update, all indexes will be r (...)

(...) this functionality and provides instructions for its use.     Assumptions, design and configuration The fundamental objective of the global logout functionality is to enhance user Security by preventing unauthorized access to the system. Previously, there were instances where, despite logging out of Portal, the user's session remained active, e.g. on another device, potentially all (...)

(...) 2024 R1 and above; author: Konrad Keppert 1. Introduction Upgrading to a newer version is inevitable for any WEBCON BPS environment due to the acquisition of new functionalities, bug fixes, and Security patches. It is therefore in the interest of the system administrator to become familiar with the capabilities of the WEBCON BPS installer and to master the procedure for upgrading the environment. (...)

(...) es the implementation of the accounting system. Step 8 (final, negative): Rejection Description: The Manager rejected the system due to unsatisfactory test results, existing errors, detected data Security threats, etc. They may also roll back the workflow to the "Initial review" step to select another accounting system that meets the defined functional requirements. The diagram of the wor (...)

(...) Microsoft account information. Fig. 9. The Sign in window After correct login, the control changes the displayed information. The mechanism supports MFA authentication if the tenant's Security policy requires it. The SSO mechanism is also supported – the logged-in user will not be asked to provide data again. Fig. 10. Control confirming user login   It is possible t (...)

(...) Applies to version: 2025 R1 and above; author: Łukasz Maciaszkiewicz   Introduction The 2025 R1 version of WEBCON BPS introduces support for SIEM (Security Information and Event Management) providers. This article explains how to integrate the WEBCON BPS platform with a SIEM service using the Microsoft Sentinel tool.   What is SIEM? The SIEM (Security Information and Event Ma (...)

(...) user list during the BPS installation. However, the configuration on the WEBCON BPS side can also be done at any time after the installation of the system, as described later in this article. For Security reasons, we recommend creating two applications – one to handle authentication and another to retrieve the BPS user list. Let's start with the authentication application. In the App r (...)

(...) on: 2025.1.x and above; author: Grzegorz Straś Related Documentation The 2 areas relevant to setting up this feature are the Visibility tab in the configuration of each form field, and the Security node in the global parameters, where the authorization methods are enabled. This article references only the minimal configuration required, but a full writeup of each page is available in the docume (...)

(...) also be paid to the $connectionString variable, which represents the connection parameters to SQL Server that should allow reading data from the content database. In the example, the "Integrated Security =True" parameter is set because the service account in the context of which the PowerShell script is being run has read privileges to the content database.  In other cases, special SQL crede (...)

(...) best possible software. With each release, the platform is developed according to the highest industry standards and subjected to rigorous testing procedures to ensure stability, reliability and Security . Each major release of the platform (e.g. WEBCON BPS 2025) is supported for 12 months for bug/error fixes and improvements. In addition, each major release of the platforms is also suppo (...)

(...) wryał   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: Security | WEBCON BPS SMS notifications | WEBCON BPS   Introduction SMS notifications in WEBCON BPS are one of the methods for additional authentication of user operations, e.g. when authori (...)

(...) tionality prepared in this way will be able to be embedded into the site as an IFrame.   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 offi (...)

(...) ---------------------------- CallStack ------------------------------------------------------- at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity , RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurity Checks) at System.Reflection.Runti (...)

(...) I tried to import some templates from DEV environment to TEST environment and when I uploaded the .zip archive the following error occured on the .xlsx report: "Value cannot be null. Parameter name: Security Provider" Does anyone know why do we get this error? Thanks!

(...) everyone, because the first installation attempt did not work out (login problems webcon designer studio), i uninstalled webcon and sharepoint. I installed Sharepoint 2016 again and also the latest Security update. Now the installer does not recognize the sharepoint web parts (see picture below). Did anybody have this issue yet? Do you have any idea how to fix this? Is it ok, to skip this? Kind rega (...)

(...) ute as the server principal because the principal "BPS_readonly" does not exist, this type of principal cannot be impersonated, or you do not have permission. the BPS_readonly account exists in DB\Security \Logins and has access to the Content database. How to fix it?