search results

(...) Applies to version: 2024 R1 and above; author: Łukasz Maciaszkiewicz   Introduction Designing a business application is a process that requires both good memory and coordination from the people involved in it. Unfortunately, when faced with a large number of tasks, lengthy execution times, many people involved, or often all of the above, even the most capable mind must yield. To address th (...)

(...) the same machine via WEBCON BPS installer (in a previous version). When these three components are installed on the same machine (Designer Studio and the database can be separate) the installation process is simplified. Launch the installer on the machine where the components are located, and simply go through the suggested steps. All steps of the installer will be carried out automatically and do (...)

(...) e   Should we import applications via an application instead of the Designer Studio? In my opinion yes. But this is mainly influenced from a partner perspective who has to deploy the same process to multiple customers who require that these kind of things are documented. What would be the benefit of having an application: When something is automated, it can be tested, and therefore t (...)

(...) ason, it is good practice to plan the environment in advance, detailing the system components, their network addresses, and communication between them. The following diagram shows the installation process described herein, along with the addresses of each service.   The example uses Docker Desktop. All basic components of WEBCON BPS can be installed there. Only the system's database (...)

(...) Starting Webcon journey usually begins with moving some data from other places, let it be SQL databases, but when more applications are created you still might need this knowledge to migrate further process es. In this series I'm creating an example application into which I'm importing data using built in cyclic actions, and external powershell script using REST API. Creating example appli (...)

(...) le examines the admin mode in Portal and the capabilities of users with Business administrator privileges. In addition to detailing the specifics of the aforementioned mode, the article addresses the process of granting Business Administrator privileges and configuring rules that include the Is admin mode active? variable.   Who is the Business administrator? In simplest terms, the Business (...)

(...) rules in the Nlog section The configuration above specifies what information is saved and at what level, while the Nlog library determines how this information is recorded. It collects entries, process es them, and finally saves them in the appropriate database table (AdminWFEventLogs). Without this, the entries would only be displayed in the console. The library configuration contains two rules (...)

(...) be saved in an empty category.   However, with the release of version 2023.1.3.231, this restriction has been removed. Now, it is no longer necessary to define attachment categories in the process to save attachments in a dynamic category. This change simplifies attachment management, allowing greater flexibility in using dynamic categories.

(...) l(integerInput, "max", max); nxWebcon.integerRange.addAttributeIfNotNull(integerInput, "step", step); integerInput.attr("type", "number"); integerInput.attr("oninput", "nxWebcon.integerRange.process Changes(this)"); } nxWebcon.integerRange.addAttributeIfNotNull = function(integerInput, attributeName, value){ if (value != null) integerInput.attr(attributeName, value); else in (...)

(...) ment, we can precisely place the signature where it’s needed. Additionally, the interface allows for navigation between document pages, providing flexibility and control over the entire signing process . To configure this solution, three essential business rules are required: Attachment Retrieval Rule: This rule gathers the names, IDs, and content of the attached documents.   (...)

(...) CON BPS License activation.   2.3 Updating SDK plugins The SDK plugins are only compatible with the major version of WEBCON BPS for which they were created. If SDK plugins are used in the process es, and the environment will be upgraded to a newer major version (e.g. 2023 à 2024), it is necessary to prepare a new version of them that is compatible with the SDK requirements for the targe (...)

(...) ities create an additional layer of visualization of the workflow, making it more transparent and easier to understand. This article describes these functionalities using a sample workflow for the process of implementing a new accounting system.   Business case The sample workflow for the process of implementing a new accounting system includes 3 phases, 8 steps, and 3 actors. Below is a (...)

(...) uthentication configuration, there is no need to duplicate the values here. The scopes field remains empty. Fig. 8. OAuth2 Authentication form field configuration   After saving the process , a new form field will appear on the form to allow login. After selecting the Sign in button, the system will connect to Azure and display an authentication window. In it, the user should enter their (...)

(...)         "Enabled": true           },           "process Instrumentation": {             "Enabled": true           },   (...)

(...) re authentication on the WEBCON BPS side.   Registering the Microsoft Entra ID user list synchronization application The next step is to create a second application that will handle the process of retrieving the BPS user list. Registration of this application is similar to the previous one, except that in this case there is no need to complete the Redirect URI. Now it is time to (...)

(...) required to make sure that business rules and form rules work correctly since those could be based on fields that require access authorization.   Limitations on Dashboards, Reports, and in process Configuration At the time of writing, there is no way to easily authorize outside of the form. Because of this, using form fields with access authorization configured is not possible in certain pl (...)

(...) :00 PM; Current date: May 1, 2025, 4:00 PM; Interval: 2 days Timer dates: May 4, 10:00 AM; May 6, 10:00 AM; May 8, 10:00 AM   Summary Timers are a tool that highly automates business process es implemented using WEBCON BPS. The date and time at which a timer is activated and re-executed can seem difficult to predict. However, in order to take full advantage of this functionality, it is es (...)

(...) ig. 1. “Flagged” task   Fig. 2. “Postponed” task   Providing users with the option to flag tasks does not require any additional settings at the process level, as long as the Task details section is visible on the form.   Changing the flag from the workflow instance level Changing the flag from the workflow instance level is possible in (...)

(...) he original post has appeared on daniels-notes.de If you are using JS/CSS to improve the user exeperience a bit there are two different situations: It's global and can be reused in other process es It needs to be adapted for each process . If something changes in a new WEBCON BPS version, the second situation may cause a problem, because you don't know where you used the same approa (...)

(...) pts in Azure Communication Services - An Azure Communication Services concept document | Microsoft Learn.   SMS vs. operation authorization If additional authorization is enabled in the process configuration (path transition authorization, confidential form data access authorization) and the specified authorization method is SMS, according to the above configurations, a one-time authorizati (...)