User Voice

I strongly support this idea, as I'm working on a new offer, where one of the requirement is the exclusion of people/groups from a permission. I would suggest the there should be also the possibility to revoke permissions on item level.

Hi,

it would really if we could create inline "data sources" for the running mode `Get data from data source` if the source is a SQL database. Reasons:

- It would be similar to data tables, where you can write your own SQL, so the user experience will be similar
- We don't bloat the SQL data sources, if this source is only used in a single case.
- While SQL server does a great job on improving queries, there will be times, where the `predicate push down` which moves the filters from the outer to the inner SQL query will fail. Therefore, this will create a higher load on the server than necessary.
https://daniels-notes.de/posts/2026/user-defined-api-part-2-get-data-from-data-sources#sql-server-predicate-pushdown



Best regards,
Daniel

Is any change planned within that area? Our IT Director also recently asked about that possibility :)

Hi,

the default data source `<Users and Groups>` currently appears to have a direct impact on the `CacheOrganizationStructure`. This behavior is unexpected and can lead to severe administrative issues.

The **User List Synchronization Configuration** already provides an **Advanced** tab where synchronization filters can be defined. Because of this, it is not obvious why additional filters configured on the default `<Users and Groups>` data source also affect the synchronized user and group cache.

For example, adding a simple **Group Members** filter to the `<Users and Groups>` data source, with the intention of displaying only employee accounts by default in user pickers, causes users and groups outside that filter to disappear from the `CacheOrganizationStructure`. As a result, even WEBCON developers and administrators can become inactive in the cache and lose access to both the Portal and the Designer Studio.

This coupling between the presentation/filtering behavior of the `<Users and Groups>` data source and the internal user synchronization mechanism is difficult to understand and can easily lead to accidental lockouts.

**Suggestion**

Please decouple the default `<Users and Groups>` data source filters from the synchronization process and the `CacheOrganizationStructure`.

The data source filters should only influence what is returned by the data source itself, while user synchronization should be controlled exclusively by the dedicated **User List Synchronization Configuration** (including its existing **Advanced** filters).

If this coupling is intentional for technical reasons, it should at least be clearly documented in the Studio and administrators should receive an explicit warning before configuring filters that may affect the synchronized user base.

This change would make the behavior much more predictable and help prevent administrators from unintentionally locking themselves and other users out of the system.

Kind regards
Sébastien

PS: If anybody runs in this problem one can use this file on the application server "C:\Program Files\WEBCON\WEBCON BPS Designer Studio\WEBCON BPS System Administrators\WEBCON BPS System Administrators.exe" to activate admin access to the Studio and to delete the filter in the default data source `<Users and Groups>`.

Hi Daniel,

I just kept my examples simple. I fully support your point with descripting path/button names.

But even there you can have multiple processes just using „Reject as QM responsible“ eg. The path name catalog could store all those names and make them selectable with autocomplete.

Kind regards
Sébastien

I'm also for a less hacky option to apply colors to paths, so I get rid of my approach. Add a simple css class to the path element based on the selected color would solve this:

https://community.webcon.com/forum/thread/2181?page=1#m2187


Off topic:
These kind of names are a "no-go" for me. Always use a more descriptive way to inform the users what will happen. Let's imagine a multi approval step workflow and users can have different roles in this.
If we have only "Reject" or "Approve" the user needs to first understand which role he currently has.

If we use a more elaborate naming for the path, it's way more easier:
Reject as QM responsible
Reject as cost center owner
Approve and forward contract to customer

This makes it also easier to choose the correct "Reject" path from the variables in Designer Studio.

Best regards,
Daniel

Would it be possible to add a simplified view option via a button on the top bar that would display a different view of the form?
This could work similarly to the OCR preview, where I could select which modules to hide—for example, attachments and comments.
An example from my own experience is the invoice verification process. Users suggested that it would be helpful to be able to collapse the view using a button on the top bar, just as they can do during the OCR verification step, where the preview is hidden and they can quickly return to it by clicking the button on the bar again.

Hi,

it would be very helpful to have a centralized path name picker in WEBCON BPS.

Instead of naming each workflow path manually and independently, devs could select predefined path names from a central configuration, for example:

* Close
* Cancel
* Save
* Approve
* Reject
* Send back
* Forward
* Archive

Each predefined path name should also allow translations and assigning a default path color.

For example:

* Cancel → red
* Save → green
* Close → grey
* Approve → green
* Reject → red
* Send back → orange

When a path name is selected from the picker, the corresponding color should be applied automatically.

The path name picker should offer an autocomplete unique name list with all known path names of the environment.

Benefit:

This would improve consistency across applications and workflows. Common path names would no longer have to be maintained individually in every workflow. It would also reduce configuration effort and avoid inconsistent naming such as “Cancel”, “Abort”, “Close process” or “Stop workflow” being used differently across applications.

A central path name and color configuration would support better UX, clearer process design, and easier governance in larger WEBCON environments.

Kind regards
Sébastien

Hi,

I suggest to provide Concierge as Microsoft Copilot agent and a Concierge interface to be embeddable via an iFrame, so that it can be seamlessly integrated into corporate intranets, portals.

This would enable organizations to provide a unified user experience, make Concierge more accessible within existing digital workplaces, and support a wider range of use cases without requiring users to switch between applications.

Benefits:
* Easy integration into intranet portals and dashboards
* Seamless access to Concierge within existing workflows
* Support for Microsoft Copilot and other AI-powered agent experiences
* Increased adoption through a consistent user experience
* Reduced navigation effort for end users

Kind regards
Sébastien Anselment

Hi,

it would be nice, if I could omit the element id in the "GET" request of a 'Action on a workflow instance' running mode. This would be more similar to other APIs and it wouldn't make it necessary to create a separate 'Get data from data source' endpoint.
If OData support / paging would be added to this running mode, it would be even better.

UDA: OData support
https://community.webcon.com/forum/thread/8661/15

UDA: Add paging to 'Get data from data source'
https://community.webcon.com/forum/thread/8660/15


Now it's time to had back to the DACH WEBCON DAY. :)

Best regards,
Daniel