search results

(...) e same managers, and this leads to trouble in maintaining - i have two places to update, that's why I'm creating Global rules instead. (I like 'em DRY) It would be great to have a 'Promote to Global scope ' button on Business Rules, Constants, Automations, Action Templates etc, so we could just move those to a scope , which is available for all processes (unfortunately not in an application, but whole s (...)

Below you can find the latest version of WEBCON BPS 2019 and the full changelog for it. Please note that this version is no longer supported. We apologize for any inconvenience caused.  Our latest major release is 2026.1 – [Whitepaper – Business overview]  (Latest build: 2019.1.4.260) As we strive to improve our software continuously, we

(...) ileges. The privileges defined for the application allow you to specify groups of users who can modify their definitions and processes assigned to them. Within the application’s privileges, the scope of their visibility to end users is also defined. To set privileges go to the selected application and select the User privileges section. The application has the following levels of p (...)

(...) selectable values to the form field directly from our WEBCON BPS Dictionary process – to which we can add values in the form of workflow instances at any moment. And thus we can enjoy the full scope of functionalities provided by dictionary processes.    

(...) used to obtain the authorization code. In the following call you must replace {ClientID} with the correct Client ID described in the previous chapter. https://accounts.google.com/o/oauth2/v2/auth?scope =https://www.googleapis.com/auth/drive&response_type=code&state=security_token%3D138r5719ru3e1%26url%3Dhttps%3A%2F%2Foauth2.example.com%2Ftoken&redirect_uri=http://127.0.0.1:80&client_ (...)

The WEBCON team works tirelessly to improve the WEBCON BPS platform. We constantly strive to fix any errors and make sure that our system always functions as intended. Every year, we publish a so-called ‘big’ version which introduces a multitude of new features. Additionally, updated builds are released at least once a month, they aim to resolve any existing issues and implement sma

The WEBCON team works tirelessly to improve the WEBCON BPS platform. We constantly strive to fix any errors and make sure that our system always functions as intended. Every year, we publish a so-called ‘big’ version which introduces a multitude of new features. Additionally, updated builds are released at least once a month, they aim to resolve any existing issues and implement sma

Below you can find the latest version of WEBCON BPS 2021 and the full changelog for it. Please note that this version is no longer supported. We apologize for any inconvenience caused.    Our latest major release is 2026.1 – [Whitepaper – Business overview]  Important: Before upgrading from one complete version to another (

(...) Logout URL - after logging out, the user will be redirected to this address. It can be left blank as it is not obligatory. In this case, the user will be redirected to the BPS Portal login page. scope - list of data necessary for BPS to identify the user. “Profiles” and “email” are already added by default. For other OpenID server implementations, you may need to add differ (...)

(...) tion One of the available types of substitutions in WEBCON BPS is Task delegation substitution. Thanks to this functionality, tasks can be performed for an absent employee, while ensuring that the scope of rights granted to their Substitute is limited to the required level, without violating e.g. company secrets. This article describes the rules for configuring Task delegation substitutions, taki (...)

(...) vanced configuration of the person or group field in the choice field with a search option mode –  General tab   In the “Picker” tab, one can additionally define the scope of the data originating from the organisational structure that should be available in the choice field; the number of people, domain groups as well as BPS groups can be reduced (Fig.14). By applying (...)

(...) set of privileges that must be granted to the application used by the authentication provider for the correct operation of the login component. Note - administrator's consent for the privileges (scope ) is required.     After creating the provider and granting the necessary privileges, you can start implementing the Microsoft Graph Toolkit components in the WEBCON BPS Portal. (...)

The WEBCON team works tirelessly to improve the WEBCON BPS platform. Please note that this version is no longer supported. We apologize for any inconvenience caused.  Our latest major release is 2026.1 – [Whitepaper – Business overview]  WEBCON provides full technical support for our two latest major versions. Important: Before

(...) n analytical integration talks. The Customer/Integrator verifies the data structure and data quality (whether there is a unique key or data is not repeated etc.) While carrying out the study, the scope of the data required for implementation (see chapter “Examples of Views”) will be specified. The Customer/Integrator is responsible for the delivery and quality of the data. The data (...)

(...) Figure 8. Authentication configuration In the authentication section select the previously created connection, set “grant_type” parameter to password authentication, and define the scope , i.e. specify the area to which the application has full access.   Figure 9. Request body configuration     “Request body” is the next section. Here, att (...)

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

(...) cation will obtain data (we will assign privileges later). Client ID: Keep this! You will need it later. Client Secret: Generate and keep this! You will need it later. Application permissions (scope s): App.Odata.Read.All     To finish setting up the API Application, place the Login from its configuration into the privilege settings of every application and process you wi (...)

(...) his is a kind of data source that often reduces the need to thoroughly check the workflow configuration in the system. However, it should be borne in mind that, unless certain conditions are met, the scope of information available in History may be broader than at individual workflow steps. Therefore, the workflow should be carefully designed, paying particular attention to the privileges granted to us (...)

(...) n be used in both standalone and cloud installations. The Export-Import mechanism makes it possible to transfer BPS groups with the application to another environment, and in WEBCON BPS 2023 R1, this scope has been extended also to Group owners. This article shows an example of such a migration.   Configuration For the purpose of demonstrating how the BPS group transfer works, a group nam (...)