Skip to main content
Version: 2025 R1

Global parameters

The node contains various settings and options that apply to the WEBCON BPS system globally. The window displayed after selecting the node allows you to configure a number of basic parameters. The node also groups in subnodes more complex functions – after selecting a subnode, the user gains access to advanced configuration of a given function.

drex_SystemSettings_GlobalParameters_screen.png

1. Environment settings​

Environment unlocked, full ability to edit​

The purpose of blocking an environment is preventing divergences between environments caused by small changes, e.g. made directly in the production environment, without first introducing them on testing and development environments.

Once an environment is locked, it is still possible to update processes by means of the Import function. In such case, the process is saved as usual. Moreover, it is still possible to edit certain fields for testing and verification purposes, e.g. prompts that have a Test button attached, but it is not possible to save those changes.

Please find below the Process configuration items that can be modified in the locked environment:

Environment locked, ability to edit restricted​

When an environment is locked, it prevents the saving of changes in the Process configuration (with the exceptions listed below) and Data sources. In both cases, you can modify parameters to conduct tests, but please note that these changes cannot be saved.

Once you lock an environment in the System settings tab, it is not possible to edit the following items:

2. Substitutions​

Substitutions enabled​

Once selected, the checkbox activates the following options:

  • Time mode – the setting allows you to choose the mode for displaying substitutions and processing time. Selecting the daytime mode will irreversibly convert all dates to daytime dates.
  • Update tasks for substitutes – clicking the button will trigger an update of tasks for substituting individuals in the current content database. The assigned tasks will align with active substitution definitions in the automatic task delegation mode.

3. REST Service​

Activate REST Service​

By selecting the checkbox, you gain access to BPS instances via a smartphone.

4. Database acronym​

Current acronym​

The unique identifier of the process database consists of 3–6 alphanumeric characters. This identifier is crucial for distinguishing to which process database an instance belongs. It is used in 2D barcodes and for e-mail correspondence tracking through the WEBCON BPS add-in for Microsoft Outlook.

5. Business entities structure​

Default business entities structure​

Choose the source from which the data regarding the business entity structure will be retrieved.

6. Applications IDs in external systems​

Google API key​

In order to work correctly, the Google Map form field requires a key. In order to get a Google API key, follow the steps described here. Next, enter the obtained key into this field.

Power BI application ID​

In order for Power BI reports embedded in WEBCON BPS Portal to function correctly, you must provide a correct Application ID identifier. To obtain an Application ID, complete the registration of WEBCON BPS Portal in the Azure AD service.
You can complete the registration using the Power BI App Registration Tool available here or directly in the Azure portal.
During the registration, as the Redirect URL provide the address in the following format: (WEBCON BPS Portal address)/powerbiredirect, e.g. https://webcon.com/WEBCONBPS/powerbiredirect.
Additionally, in the Azure portal, you must activate the Access tokens in the authentication configuration of the registered application.
The full guide for application registration can be found here.

7. Microsoft Graph API​

Cloud type​

The parameters of API Microsoft Graph used in the integration of WEBCON BPS with Microsoft Cloud services are associated with the cloud type specified in the configuration. The integration involves the following functionalities:

  • AAD-based authentication,
  • users and groups synchronization,
  • integration with Exchange Online (e-mail notifications, administrative notifications, HotMailBoxes, MailApproval, dedicated actions),
  • integration with OneDrive,
  • Microsoft Graph built-in authentication.

Basic parameters specification for cloud types available in the system:

8. Required mobile application security level​

Level​

The parameter defines the minimum security level for the mobile application. The application security level can be imposed in the configuration by choosing one of the following options:

  • User defined – the security level of the mobile application is not imposed and depends solely on the application user's profile configuration (it is possible skip any security measures),
  • Application must be secured with a PIN code – when launching the application, it is necessary to enter the PIN code that is common for all the user profiles.

9. Push notifications​

Activate mobile push notifications​

The checkbox activates PUSH notifications for mobile devices.
When the option is enabled, the WEBCON BPS Workflow Service sends PUSH notifications to all mobile devices that have been configured to receive them. In order to receive PUSH notifications, the mobile application user must configure PUSH notifications on their profile. Notifications are sent whenever a user’s task-count changes (e.g. when a new task is created).
In order for a service to handle PUSH notifications, it must have the Basic features service role enabled in its service configuration.

caution

PUSH notifications for iOS require WEBCON BPS Workflow Service to be launched on a server with Windows Server 2016 or later.

10. Diagnostic logging mode​

Level​

Enabling the diagnostic logging will cause the system to log additional events in order to analyze errors and system performance more accurately.
There are three available diagnostic modes:

  • Off – when selected, the diagnostic mode is disabled,
  • Trace – saving the workflow instance and transitioning it between steps (via paths) will be logged in the WFHistoryElementTraceLogs table. Based on the logged information, it will be possible to analyze which path or step is the most time consuming,
  • Debug – diagnostic information is logged in the AdminDebugLogs table, enabling full system diagnostics. Enabling this mode will cause a significant drop in performance.
caution

Enabling diagnostic mode can cause reduced system performance, therefore it is not recommended to keep it enabled on the production environment for extended periods of time.

info

To learn more about enabling the diagnostic logging mode, read the ARTICLE available in the WEBCON Community website.