search results

(...) I’ve been wondering why Webcon doesn’t support Git integration. It could really help speed up the dev elopment of new features in workflows and make it easier to fix any critical bugs quickly. Webcon team — Git support would be a game-changer. Please consider adding it!

(...) erences. Benefits: Clearer identification of the portal context when multiple applications are open. Improved user experience, especially in multi-tenant or multi-environment setups (TEST, PROD, dev ). Easier navigation and task switching for users working across several portals.

(...) Equipment dictionary that stores unique records for items used in field operations outdoor. I need to determine whether it is possible to configure WEBCON BPS so that scanning a QR code with a mobile dev ice (via phone camera ) can directly open the corresponding dictionary instance. The key requirement is that the QR code is generated by an external system, not by WEBCON. In other words, a pre-prin (...)

(...) d well-designed solution that all most meets our needs. Like many other organizations, we handle sensitive data that should not be stored in plain text in the SQL database. To address this, we've dev eloped a simple SDK-based customization of a form field that displays the field value on the form, but stores it in an encrypted format in the database. Unfortunately – and to our disappointment – (...)

(...) Webcon Designer Studio. They cannot even create a new data source, which is the recommended approach by Webcon when utilizing external databases. Or create a new application. It seems that Webcon dev elopers assumed that the platform would be governed centrally – by a central unit that creates new applications, grants application privileges, configures data sources, assigns licenses, and controls (...)

(...) trix. Applying the same rule to step names ensures a consistent and predictable user experience. 2. Immediate visibility of non-standard configuration Broken inheritance represents an intentional dev iation from inherited behavior. A red step name makes such dev iations instantly visible, especially in complex processes. 3. Reduced risk of configuration errors Visual indication helps detect uni (...)

(...) cal improvements over “nice-to-have” features with limited business value — quality over quantity. All feedback collected in this thread will be reviewed by the product team and considered in future dev elopment. At the same time, to manage expectations, this discussion does not imply any commitment to specific implementations or timelines. I’m looking forward to your insights! Dawid WEBCON Pr (...)

(...) Hi, I currently have two WEBCON environments (dev and PROD) running on separate machines. Due to the fact that we’re still on an older version (2023 R3), I’d like to upgrade an environment to version 2026 for testing purposes — mainly to verify stability and estimate the effort required to adapt our solutions. My idea is to set up a third environment (TEST), align it with PROD, and then perfo (...)

(...) Hi all, I was following the instructions for Form field extensions: https://dev eloper.webcon.com/docs/your-first-form-field-extension-js I got stuck at the first build step in WEBCON BPS SDK Tools, specifically here: "In order to build your Form Field Extension JS you have to select it in the appropriate dropdown in the tool and click the build button. It results in creating the BPSPKG file (...)

(...) Hi all, I have a question regardong Form Field Extension PhoneNumber, I went through instruction: https://dev eloper.webcon.com/docs/your-first-form-field-extension-js/ . My problem is I can't get intermidiate step to be executable, what I mean by that is that when I press on my Start step "Go to next step" it automatically executes and saves like already done instance and it says the workflow ins (...)

(...) wo – Poziomy dostępu. – Nadawanie ról i ochrona danych zgodnie z zasadami firmy. Publikacja i wersjonowanie aplikacji – Jak poprawnie wdrażać zmiany. – Najlepsze praktyki pracy na środowiskach dev → TEST → PROD. Diagnostyka i narzędzia dev eloperskie – Logi, monitorowanie, podgląd błędów. – Co robić, gdy coś „nie działa”. Jeśli jesteś zainteresowany pisz na adres: slawomir.heciak@me.pl

(...) Hi, it would be nice if todos would be improved. Right now it’s just a simple textfield and a structure needs to be done by the dev s. Suggestions: - Thread style - Automatic timestamp and author for each message - Cascading replies to message - Notifications when a reply to an own message has been created - Same for notes in WF Designer. If notes are seen as todos it would be better to swi (...)

(...) this mode, users could: - see the full workflow diagram - inspect steps and paths - review configuration settings of elements - analyze parameters and logic used in that version This would allow dev s to fully review previous configurations even after many subsequent changes have been made. 3. Visual comparison between versions An additional feature would be the ability to compare two version (...)

(...) ns) 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 dev s with studio access. An option to set an object as protected and enabling an app binding to allow the usage would solve this matter. Default would be same behavior as it is now. If a dev wants to (...)

(...) ts 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 dev s 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 leve (...)

(...) ded and connected with an entry path or when deleting a flow control after connecting the existing path leading to the flow control to an intermediate step. To minimize this kind of error and turn dev elopment even more efficient I suggest to mark such a path to an intermediate step e.g. with a red exclamation mark in the beginning/middle/end of the path. A warning could even prevent saving the pro (...)

(...) ource should have the same sort and filter possibilities in the dashboard as in processes. There is so much data in data sources we'd like to visualize, search, filter, ... on a dashboard. As a dev imagine a WEBCON monitoring dashboard that has lots of widgets with SQL data sources that show e.g. a mail log, login log, process log, error log, ... Kind regards Sébastien

(...) Hello, we've just updated our WebCon from version 2023.1.2.44 to 2026.1.4.125. Every time I switch between our portals (dev /test/prod environments) WebCon Designer crashes when I save the process. Afterwards I can reopen the designer and saving works fine. I check the newer releases for this error but could find a hint that this problem has been resolved. Thanks for your help! Best (...)

(...) like GIT. Core elements: - Scope Type (mandatory) Automatic assignment to the environment with different scopes of changelog details. Testers need more detailed information about changes from dev to test for quality management. Common users need details about new features, changes and bugfixes for daily usage. Multiple selection of target scope: Testing, Production - Change Type (mandator (...)

(...) In the code-parts of https://dev eloper.webcon.com/docs/configuration-attributes/#configeditablegrid In the code window below the < - sign and > - sign are showed as ' & lt ; and & gt ; ' Is this intentional ? Because the code in the documentation is C# My colleague did not notice right away but I did!