User Voice

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

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