05.03.2026
14:22
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, 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. (There is another user voice for this feature: https://community.webcon.com/forum/thread/8360)
That‘s why I suggest to insert a configuration functionality on application level next to „presentation“ entry in the tree.
Rules, automations and constants could be created and used by all processes of the app only without having to replicate identical objects in each process.
The editors „function“ tab would need a 3rd option "App form rules" between "Global form rules" and "Process form rules". Same for constants and business rules in the respective editor tab. E.g. "App constants" between "Global constants" and "Process constants" in the editors "Values" tab.
Same for automations.
Kind regards
Sébastien
