Michal Rykiert

Just for clarity: I meant we understood where you came from and gave it a proper thought.

Since this thread is more of a question rather than a development suggestion, I'm moving it to the Forum section.

Razvan, your voice has been heard. Once I have any updates, I'll let you know.

A small correction, the feature is currently under review. I marked the post accordingly.

Since the case is resolved, I'm closing the thread :).

Hello Peter, the main idea behind the archiving mechanisms is to help efficiently manage instances that are no longer actively used but need to be stored. For instance, in many countries, legal documents need to be kept despite the fact they are no longer in use. Archiving mechanisms also help

Hi Paweł, so many ideas at once :). Let me address them in order: Ad.1 "One configuration window at a time" approach was our concious decision from the very beginning. For many, such solution helps with getting things done in order, without confusion and potential double/unwanted inputs (keep

Hi Maksymilian, I see your point and we had a discussion about your request. At this point, the scope of required changes in the code is too extensive compared to the benfits we see for all clients. Currently we focus on making automated imports and further improvements, to make sure DEV-TEST-PROD m

At this point the scope of the required work is too extensive compared to the benefits we see. Thanks for the suggestion though!

Hi Daniel, could you please outline use case/use cases for the global HTML field? It would help us evaluating it internally.

We plan to introduce a functionality to display the ID in the admin mode. I cannot commit towards when exactly at this point, so stay tuned :).

We had an internal discussion about the case you brought up. The consensus is that we'll introduce a behavior that would make deactivated buinsess entities disappear from the tab menu by default. At the same time, it will be possible to display all business entities whenever necessary. We don't h

Let me provide a voice from the other side of this topic. The challenge with nested groups is the transparency. The more levels of nesting you have, the harder it is to say which users actually belong to the certain group. Of course if you're a responsible admin, you'll manage it properly. However

I'm wondering whether more people would also need this? If so, vote (click a thumbs up button)

I'm happy to say this feature is going to be released in 2024 R1 :)

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?