User Voice

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

Hi,

it would be nice to move API definitions of the running modes 'Get data from data source' and 'Execution mode'. These are running outside the context of a workflow/process anyway and while you are going through multiple iterations you may want to consolidate these.
Ok, there may be references to business rules / automations which may prevent these, but that would be something which could be checked and the user could be informed that this isn't supported in the current version.

Best regards,
Daniel

Hi,

I tried various approaches to return an actual NULL value via Execute Automation, this wasn't possible. Instead these are default values:
Text: ""
Decimal: 0
Boolean: false
DateTime: 0001-01-01T00:00:00

https://daniels-notes.de/posts/2026/user-defined-api-part-4-execute-automation#no-null-values

If I would ask an AI, whether I could use WEBCON for a specific use case, and it uses the Exceute Automation endpoint, it will get "false" even if the use case hasn't been defined.

Best regards,
Daniel

Hi,

in my version (2026.1.6.198) there are a few limitations:

- There are no time zone information.

This applies to all running modes and even if I just use a Execute Automation and return an incoming date time value, the information is lost.

https://daniels-notes.de/posts/2026/user-defined-api-part-4-execute-automation#time-zones-are-lost

If I would have a unit test, this would fail. If a travel agency send me the departure time of a flight, the user will see a completely different time, than the actual one. I could continue with this.

The client consuming the endpoint shouldn't need to have any information in which the WEBCON server operates to workaround this.

- BPS internal views strip seconds

https://daniels-notes.de/posts/2026/user-defined-api-part-2-get-data-from-data-sources#bps-internal-views-ignore-seconds

Best regards,
Daniel

Hi,

it would really be helpful if OData support could be added to the 'Get data from data source' running mode. This would allow to add custom filtering on addition to the one configured in WEBCON.

Best regards,
Daniel

Hi,

the result of a 'Get data from data source' UDA is limited to a 1000 records. I can understand the reasoning but implementing a custom paging option for each endpoint is cumbersome. It would be great, if this would be handled by WEBCON.

I'm currently using one of these approaches:
https://daniels-notes.de/posts/2026/user-defined-api-part-2-get-data-from-data-sources#simple-paging-for-99-of-cases
https://daniels-notes.de/posts/2026/user-defined-api-part-2-get-data-from-data-sources#complex-paging-for-100

Best regards,
Daniel

Hi,

while I can image that there are currently higher priority tasks than improving the change control (change history) it could be a low hanging fruit to offer a small dialog in which we can store two/three fields which will then be saved in the database with all changes. For example, this would allow us to store a. Azure DevOps User story id and task id and maybe define it or change or bug. I would be fine with having simple text fields other may put there Confluence Epics or whatever.

While it would also be nice, if this dialog would be displayed, when you open the Designer Studio it doesn’t need to. Those companies who need this will just have to make a habit of putting their information there.

Then every one of us would have an option to identify the changes in the database and handle these how we need. We did try to put this information in the documentation fields, this worked for a while, especially for new features, but over time the information there got to much and became outdated, when something else changed. This laziness would be prevented by such simple dialog.

Of course, it would be nice to improve on this in the future, but this would be the first step and would allow us to prepare the data now. Ideas for improvement:
- General improvement to the change history like filtering for element GUIDs or those custom information
- New tab for each element which displays the changes and their user story/task/bug and change type
- Endpoints for retrieving the changes for a specific “id”.

While the improvements would help everyone, we can work around these on our own, but we cannot intercept/interact with the way the information is stored. Adding this dialog and saving this information probably be an easy change and offer the companies a lot of possibilities.

I have no idea, why I didn't come up with this idea years ago. :)

Best regards,
Daniel