User Voice

Sometimes an Item list isn't the best way to display data, it would be better to display in the default stacked format. If you want your data to look this way you can't utilize the Autocomplete Field Type. The ability to disable adding rows in an Item List somewhat covers this, but having the ability to use an Autocomplete within a Group would let users have the same search experience regardless of if fields are in an Item List or a Group. Thus allowing both form factors to function the same way from a user perspective.

Hi everyone,

I would like to suggest an improvement to the standard archiving mechanism in WEBCON BPS.

Currently, the standard archiving functionality works well in two important areas:
- links to archived elements remain the same as before archiving,
- archived elements are moved to a separate archive database, which helps reduce the amount of data processed in the main database and improves performance.

However, there is one very important business requirement that is currently not covered:
- Archived elements should preserve the same read permissions they had before being moved to the archive.

In many real-life business processes, permissions are not global or static. They are often assigned individually to each workflow element based on:
- the author of the element,
- process participants,
- actions executed during the process,
- the path the element followed,
- business-specific permission logic.

This means that every element can have a different permission set depending on how it was processed.

For some organizations, granting broad/global access to archived elements is not acceptable due to security, compliance, and confidentiality requirements. Manual permission assignment is also not realistic when dealing with large volumes of archived data.

We have already consulted this case with WEBCON. Based on the analysis, this scenario cannot currently be handled using standard configuration, SDK extensions, or REST API. Modifying the archive database directly is not recommended and would be risky, especially because archiving is asynchronous and processed through a queue. This creates a risk of inconsistency between permissions at the time the item is queued for archiving and the moment it is actually archived.

WEBCON also suggested creating a User Voice request on the Community portal, as support from other users may help prioritize and speed up the introduction of such functionality in the product.

Because of this, I believe WEBCON BPS should provide a standard, supported way to preserve item-level read permissions during archiving.

This would make the archiving feature much more useful in enterprise scenarios where performance optimization must still respect existing security rules.

I think this would be valuable for many WEBCON BPS customers who need to archive large amounts of data without compromising access control.

Please vote if you also need archived elements to keep their original permissions.

Hi!
Please make it possible to to switch off character escaping of result text in business rules!
Or at least allow to use RAW mode for local variables in automation.
It causes problems when you prepare api call body with business rule.
Only workaround I know it to use update content into a formfield and refer it with RAW mode in API call action.
Thanks!
Peter

Hi,
please make the flow control icon smaller (or resizable). Its huge - compared to the rest of the step-icons (see picture)
Thanks!