search results

Applies to version 2020.1.x, author: Dawid Golonka   Introduction Actions are commonly used in WEBCON BPS to design the processes and individual workflows. They are performed without any user interaction and defined on the transition paths or steps. An example actions perform such activities as calculating the field value, making an entry to AD, sending an e-mail. While wor

Applies to version: 2022 R3 and above; author: Łukasz Maciaszkiewicz Introduction   To make item list more readable and user-friendly from 2022 R3 version WEBCON BPS introduces alternate colouring of item list rows. The solution allows for easier distinction between rows, which is especially important in the case of large item lists. The article describes this functionality and

(...) ased on more complex conditions that can also refer to form field values. The whole configuration allowing users to define the time the “On timeout” automation is run is called the “insert condition ”. At the transition from one step to the other the “On timeout” automation “insert condition s” are recalculated. As a result, old conditions are deleted and new ones (...)

Applies to version: 2021.1.x and above; author: Konrad Wojtycza   Introduction WEBCON BPS Designer Studio allows users to configure global business and form rules. As global rules, they are available for all applications created in a given environment and thanks to parameters they are universal and may be used in multiple processes.   Global business and form rules can be

Applies to version: 2022 R4 and above; author: Łukasz Maciaszkiewicz   Introduction In WEBCON BPS system applications, processing values entered by end users in forms is a fundamental function, alongside data gathering and analysis. The system offers several solutions to quickly and easily define arithmetic operations on values entered in form fields. This article provides examples

Hey there. What's your preferred way of hiding form fields on page load? In my scenario form fields should remain hidden, unless a form field rule from another field was triggered on value change that 'unhides' the target form field. I've been doing it the following way: 1. Make the field that should not be shown upon form load visible in the Field Matrix 2. Insert the 'Hide' JavaScrip