Michal Rykiert

Hi Bjorn, as far as I know, this scenario is already known and worked on (if not fixed already). I'll post an update once I have concrete info. Please note that bugs should be submitted via our support portal: https://support.webcon.com where they are reviewed, tested, and addressed accordingly.

I see. From the technical and UX perspective there's one challenge related to the placement of such information. Since every column on our reports can have an additional value below (like sum, average, etc.), the placement you suggested on the screenshot is already reserved for those values. At th

Got'cha!

The idea itself is good, although some companies will definitely want to preserve the historical data, including the information about permissions. Therefore I'm not sure if removing the tab is feasible. With that said, we'll see if there's anything we can do here.

Hi Daniel, in which area of the system do you experience a need of the ID?

I understand the case. As proven in this thread, it's somewhat a matter of preference how to solve it. We'll take it into account during the work on UI/UX, although to be very transparent it's a low priority at this moment.

Hi Lena, I hear you. What I can say is that we're actively working on improving the graphical workflow designer in Designer Studio. We'll take your suggestion into account. You should expect improvements in one of the HotRefresh releases of 2024 version.

Hi Lena, could you please describe what is the business case behind your request? I understand the technical side of it, I'd like to understand more the impact on the end-users.

This feature request is already in our backlog and we're in the process of defining a priority for it. I'll try to update this thread whenever I have more information.

Currently, if you disable e-mail conversation from the global form template, then the users can select to which category the e-mail should be attached to and will display there. Is that sufficient for your business case?

It certainly makes sense to have an HTML field available as a global field. We'll evaluate it against other requests and priorities.

Looking from the perspective of report usage, we put much more emphasis on reports showing current elements as they're used by everyone while reports with archived elements are used only by a fraction of users. With that said, I agree that it makes sense to have the feature you suggested in the ar

The reporting options you mention are system's standard, to be available for any client using WEBCON, without any additional effort needed. As a result, we need to thread carefully with any modifications as they'll impact virtually everyone. With that said, we are currently working on UI/UX improvem

Maksymilian, I hear you :). We're currently working on an overall major Portal revamp. I've already made sure we take your suggestion into account when it comes to improving the UI and UX of the system for the end-users. At the same time, please be aware the revamp project, although much desire

WEBCON is going to provide support for KSeF. You can find more information here: https://webcon.com/pl/ksef-connector/ or simply contact your account manager to get more details.

Hi Markus, have you evaluated if configuring a path as in the screenshot attached wouldn't achieve the result you're expecting?

Let me say this: it's coming :) I'll keep you posted once I can give you some indication of when.

By design, the comment field is meant to be an instantly available and simple way of adding additional information to the form. For more complex scenarios (like conditional behavior of the field) you'd need to use multiple lines of text field and then play with its behavior. You'll achieve the same