search results

(...) | WEBCON BPS Form | WEBCON BPS   Introduction Version 2025 R1 of WEBCON BPS introduced two new functionalities: Workflow phases and Workflow actors, which aim to visually divide the step s and tasks assigned to them according to the stages of execution (phases) and the people responsible for their completion (actors). Together, these functionalities create an additional layer of visua (...)

(...) he created authentication. It is important to specify the base service instance URL: "https://graph.microsoft.com". Fig. 6. Data source configuration in Designer Studio The next step is to configure the form field responsible for user authentication. The OAuth2 Authentication form field is used for this purpose. Such a form field must be visible in the step where the user can log (...)

(...) lpsettings.json file, ensuring you remove the entire default value, including the square brackets, beforehand. The connection string value should be entered within the quotation marks. Repeat the step s described in this section in the Tracing node and save your modifications. Once modified, the file should appear as follows:   {     "App": (...)

(...) Tenant ID and Client ID values that are required to configure 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 n (...)

(...) tion and Repeat in cycles, making timer configuration more intuitive. It is now possible to define timer parameters so that the first start of the timer (Start date) occurs Immediately after a step is entered, and next timers are executed at a specified Interval. Another important change was the extension of the configuration associated with the handling of validation/execution errors of tim (...)

(...) ilter.   After defining the first filter for the "Ordering party" form field, it's time to add the second filter for the "Order date" field. To do this, repeat the step s above by selecting "Order date" from the Filtered columns list. (Due to the different data type stored in this form field, there are slightly fewer configuration options available in this (...)

(...) abase. To execute such an action cyclically, you can use the approach described at the end of this article. A sample action is placed in the automation under the Menu button in one of the workflow step s: Fig. 1. Action context (menu button)   No credentials have been entered in the action configuration, so the script is run in the context of the account that runs the Workflow Serv (...)

(...) his article provides instructions on how to configure an SMS gateway that allows sending short text messages with authorization codes from the system.   Communication Services The first step to enable sending SMS notifications from WEBCON BPS is to create and configure a Communication Services resource in Microsoft Azure. To do this, follow these step s: Quickstart - Create and manage res (...)

(...) process. Therefore, changing the name of the WEBCON BPS server will prevent the components from working correctly and will require configuration changes to the environment. This article lists the step s 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 “ (...)

(...) se context the application will run.  Change, Read, and Write level permissions are required.   Fig. 3. Permissions assigned to the application pool account   The next step is to configure it in IIS Manager, where you need to select Application Pools in the left panel and then create a new application pool. You can give it any name you like.   Fig. 4. Di (...)

(...) p menu or context menu of the main global automation tree.     Once the location of the .bpa file is specified, the Automation configuration import wizard is launched. The import step s are described below.   1. Information This step displays basic information about the imported automation – its name and description. This information is editable. (To proceed to (...)

(...) | WEBCON BPS Form | WEBCON BPS   Introduction Version 2025 R1 of WEBCON BPS introduced two new functionalities: Workflow phases and Workflow actors, which aim to visually divide the step s and tasks assigned to them according to the stages of execution (phases) and the people responsible for their completion (actors). Together, these functionalities create an additional layer of visua (...)

(...)   Translating multilingual fields In Portal, it is now possible to use AI to translate individual text fields related to process configuration elements, such as the names of form fields, step s, and paths in the Process design, as well as the names of reports, their columns and views, and the names of dashboards and their widgets. This means that you can use the functionality for all field (...)

(...) . After installing this certificate on the IIS server, both the Portal and all configured hub subdomains will be secured automatically, without the need to issue additional certificates. The final step is to ensure that network traffic directed to the new address reaches the WEBCON BPS server. To do this, configure the DNS entries for the published domain correctly. After DNS propagation (once entr (...)

(...) f the solution makes it ideal for simple data retrieval as well as more advanced scenarios where actions such as registering new workflow instances, making updates, or taking the workflow to the next step are required. It is also important to note that the User Defined API does not require modifying the WEBCON BPS backend or adding new mechanisms to the system. Everything is based on the existing p (...)

(...) plified document workflow will be used, consisting of several basic stages: document preparation, manager's approval, and signing by external parties. The process begins with the Prepare document step during which a document template is generated. Next, the document moves to the Manager approval stage, where it can either be approved or rejected. After approval, the document advances to the Awaiti (...)

(...) abling existing accounts. All these operations are triggered using the Manage users action.   Creating account This workflow enables the creation of a new AD user. The form on the first step requires entering the details of the person for whom the account is to be created:   The Manage users action is triggered on the Create path. The configuration of this action is shown (...)

(...) iguration for tasks * possibility to define reminder templates:list of reminders: WHO, WHEN, MESSAGE, channel (email, sms, other ?) * you can attach reminder templates to each type of tasks (workflow step s) 2. Add escalation configuration for tasks * possibility to define escalation actions. Good to define escalation templates, list of: WHEN, WHO (roles, managers), MESSAGE, CHANNEL you can attach esc (...)

(...) Hi everyone, does anyone has an idea, how to create a timeout for existing instances? The workflow waits in a system step until the date of the timeout execution is reached. Unfortunately the insert condition was wrong, so all instances will wait there forever. One option would be to define an invisible path, which leads to the same step to trigger the timeout again. I don't like this approach. In a (...)

(...) after you opened the report, just like the grouping works in the views. For example if we have a report containing all our invoices and views for "factual check", "financing check" and "accounting step " plus a report for all our contract based payments and the step s "financing check", "paid", "not paid" which use different fields and need to be kept in a different report - it might look like this: (...)