Workflows

Version 2025 R1 of WEBCON BPS introduced two new functionalities: Workflow phases and Workflow actors, which aim to visually divide the steps 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 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.

Version 2025 R1 of WEBCON BPS introduced two new functionalities: Workflow phases and Workflow actors, which aim to visually divide the steps 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 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.

This post describes the details of managing main process(es) and subprocess(es), specifically in the areas of navigating between interconnected elements, displaying relevant data, and executing actions.

In the 2023 R3 version of BPS, WEBCON has implemented a new functionality that enhances security against unauthorized path transition .and prevents the execution of an unrequested task, such as signing a contract. If enabled, users who want to proceed to the next step must confirm their identity based on an additional authorization operation.
This article details the Path transition authorization and related system changes.

Workflow control (Branch) allows to redirect a workflow instance along a selected path. With the help of the workflow control step, we can among other things: set the logic of skipping steps, assign a task to other people, (e.g. in the case of approval) or withhold instances in step until the conditions are met.

In WEBCON BPS it is possible to search the contents of PDF attachments containing text using the ABBYY FineReader program. FineReader converts scanned documents and PDF files into editable form, and it is responsible for generating a text layer on attachments in workflows. This allows users to easily convert documents as well as search files. The article describes how you can configure the process of searching for documents based on two exemplary workflows. The “Add a text layer” action also supports .jpg and .png files. Graphic files are converted to PDF format, and then the text layer is applied. The effectiveness of such an operation depends on the quality of the image file. Searching in the content of files is also possible for .txt and .docx formats.

The article presents two workflows - the first is used to plan absence by an employee, and the second to register absence requests (using wizard). A special workflow for creating absence plans allows the employee to plan the absence (e.g. at the beginning of the year), which will then appear on the Gantt chart. The second way is to use the absence workflow generated by the absence process wizard - in this case, the selected absence plans (e.g. not approved by the supervisor or vacation leave) will be displayed on the Gantt chart.

In the WEBCON BPS 2020 version, the attachment preview window has been expanded with the option to switch to the preview of the next or previous attachment from the list of all files attached to instances. There is also the option to download an attachment directly from the preview window. Also the 'Drag and Drop' mechanism was also expanded. It works more efficiently and you can drag e-mail directly from Outlook.

Task and step descriptions are brief instructions on a form that help users complete a task. Descriptions can improve the workflow instance by reducing the number of errors and questions. They can contain basic information which helps a new user get started with the application, and also may explain the more complex dependencies between the form fields required to add attachments or selectable paths that will make the task easier to complete.
Step description. The step description is visible by default on the right part of the form but you can move them elsewhere, just like a regular form field. This section always contains the “Task details” header, the name of the step (in the case of the start step – they will be always “Start of the process”) and description created by a person that sets up the process.

For this article we will implement a simple system for dividing up tasks between a group of users, based on the following principles:
1) The task will go to the user with the least amount of tasks
2) If multiple users are tied for the fewest number of tasks, one of them is randomly assigned the task
3) There is a limit to how many tasks a user can have
4) Once all users of the group have reached this limit, tasks will be placed in a queue
5) Queued tasks will be assigned to somebody as soon as they are no longer at their task cap

The purpose is to split up the workload between users equally and not overwhelm individual users with too many tasks.