Processes

WEBCON BPS has a series of safety mechanisms preventing the accidental deletion of crucial elements. This post provides a checklist of "to-do" items whenever there's a need to delete a complex application, which usually consists of sub workflows and multiple interconnected configuration pieces.

This article explains how Substitutions are handled in WEBCON BPS with a special focus on the type of substitution, the user who creates the substitution, their role and privileges, as well as the availability of applications/processes in which substitutions are to be created.

WEBCON BPS supports barcodes as a method of identifying documents and workflow instances. Using barcodes allows to automate the process of scanning and registering paper documents. Stickers with barcodes simplify archiving documents, and based on barcode labels it is possible to quickly find the right workflow instance in the system. The main part of the configuration is preparing label templates.

With the release of version 2023.1. WEBCON BPS gained a new feature for displaying statistical information about an application / a process. In Portal, users now have a dedicated Analysis node with tabs that compile key figures and time series in the context of available applications. It is now possible to track Trends on working with the system, as well as display a Heatmap for a selected application.
This article briefly describes those new capabilities of the system, focusing on the advantages of the feature that summarizes information about working with WEBCON BPS in an enterprise.

This article lists the advantages of using the keyboard shortcut Ctrl+G in WEBCON BPS Designer Studio.

Thanks to the export/import mechanism, processes and any changes to them can be successfully transferred between the three environments: DEV, TEST, and PROD. However, changes made to global elements will not be transferred from one environment to another, unless an appropriate approach is taken. The present article describes this less common approach that should be used to successfully transfer updated global elements of a process.

One of the basic features that allow you to create WEBCON BPS workflows is the possibility to task assignment. You can assign a task to a specific group, person or business entity. This article presents how to use of user groups when assigning tasks and shows exemplary solutions for task assignment in the multiple business entities environment. In each process you can grant privileges such as start new instances, access to all instances or administrator’s privileges. When configuring business entities, it is required to create as many groups as business entities existing in the respective process.

The new version of WEBCON BPS mass e-mail notification system presents a great array of possibilities to adjust the contents and graphical solutions of mass e-mail notifications to the user’s current needs. Similar to the previous WEBCON BPS version the system administrator can define the day and time of the e-mail notification taking into account of the nature and working time of the organisation. Despite the possibility of defining the circumstances, e.g., group of addressees or redirecting the e-mail to the respective address, the previous version of WEBCON BPS 2021 mass e-mail notification system has been enriched with a vast range of new functionalities and visual solutions.

In WEBCON BPS, it is possible to limit the types of attachments that can be added to workflow instances due to their type and size. This option can be used to block the ability to add potentially dangerous attachments to the Portal such as scripts, executables, spreadsheets with macros. The restriction will be set globally for all applications/processes and all places where you can add an attachment – forms, HotFolders, HotMailBoxes, API. When specifying the attachment’s size – remember that the IIS server setting is the overriding limitation on the size of the added file.

The model way of implementing the WEBCON BPS system is to work on three types of environments. Processes are configured on the development environment, tests of the created solution are carried out on the test environment, and end-users of the system work on the production environment. Moving processes or changes in processes between environments is possible by using the built-in application import/export mechanism. Starting from version 2021.1.1, the mechanism was extended with transferring the contents of the dictionary processes and workflows for storing document templates. The addition of the ability to transfer data from dictionary processes allows for the improvement of the process of migrating applications between environments