search results

Hi, it would be nice if one could also create new groups for global fields and automations in system settings like it is for global constants, form rules and business rules. Kind Regards Sébastien

Hi, unfortunatelly global "objects" (business rules, form rules, constants, automations) have no app binding functionality as data sources have. Some global constants, business or form rules and automations may contain critical data (e.g. api tokens) that should not be useable by all devs with studio access. An option to set an object as protected and enabling an app binding to allow the usa

Applies to version: 2022.1.x and above, author: Krystyna Gawryał   Introduction Menu button is a button available in the top bar of a form in WEBCON BPS Portal, used to trigger automations added by the user globally or in a particular workflow step. Choosing this form of triggering automations allows you to maintain a high level of readability of the form – an automation (incl

Applies to version: 2023.1.x and above; author: Krystyna Gawryał   Introduction WEBCON BPS has been expanded to include the so-called Edit mode which allows users to view the configuration of processes and edit them in Portal. This feature is dedicated especially to business users who carry out their daily tasks using ready-made applications/processes, often without being able to vi

(...) wryał   Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: global automations | WEBCON BPS   Introduction global automations in WEBCON BPS are universal mechanisms that can be used repeatedly in different business processes without having to be defined each tim (...)

 External content by Sébastien Anselment, March, 2026 In workflow's global actions one can add automations that get executed "on start (cyclical)". It's hard to keep an overview of all workflows with such automations through all application groups, applications, processes and workflows. To get an overview one can create an MSSQL data query with the current database

(...) rocess level, but exposed to be used in other applications. This would allow us to create somewhat like interfaces, so applications won't be so tightly tangled up together. It's achievable with global automations , but this way it doesn't directly tell us which process is the parent/owner. I'm curious how you would handle this case, and if that separation of concerns is something you'd like to have ;)

Hi, At first the challenge - I'm currently reaching max # of Choose fields in my process. Trying to avoid future troubles I'm adding new workflows in a new process, and this leads to massive amount of duplicates of: business rules, constants, automations (fortunately not form rules). Let's say i have a business rule which contains some users call it 'Manager Role' - inside of the app, there

Hi, right now configurations are process specific and contain amongst others business rules, form rules, constants, automations. If multiple processes of the same app or even other apps need one of those there is the possibility to create a global equivalent in system settings. Unfortunatelly global objects have no app binding functionality as data sources have. Some global constants, busine