Michal Rykiert

We understand the idea, but after consideration there are many more things with higher priority. Therefore I'm changing the status to "not now".

As for now we're not planning any changes to the priviliges, so I'm changing the status to "not now.

Due to the complexity of item list management under the hood and other development priorities, we need to put it to the backburner for now.

Good point. I'm putting it straight into to the backlog.

We'll look into it closer. I'm changing the status accordingly.

Since the answer was provided and there's no further questions, I assume we can close this thread.

Update: we decided not to proceed further with this idea. We may re-visit it during other UI-related projects.

Short update: we had a recent decision about not extending the tooltip functionality, so I'm changing the status accordingly.

Good idea, we'll work on it :). I'm changing the status to "in backlog"

Agreed. It goes straight into the backlog and you should expect results fairly soon :).

Well, it's a good idea, and at the same time quite a complex functionality to implement as it requires some fundamental changes to the archiving mechanisms. With that said, I'm changing the status to "under review", although I can say upfront it may take us a good while before we proceed with the ne

After analysis we decided other functionalities will be prioritized. With that said, we may re-visit the idea in the future.

On top of the horizontal layout of fields on the form, there's an option to wrap them. With that said, we're not planning on extending the capabilities of the horizontal layout at this point since it potentially impacts the display of the system on various devices and in various sizes.

Hi Dawid, Many of the improvements you listed will be introduced in 2025.1. As for the rest (mainly search-related), it's not something we're able to do in the nearest future.

Let us see what others think about it. Please give a thumbs up if you need this as well.

Since Daniel has presented a good solution to the problem, I'm closing the thread. Thanks Daniel :)

That's a good idea. We could also use the field content for notification purposes. It goes straight into backlog.

Noted. We'll verify the feasibilty against other projects. I'm changing the status to "under review"

Hey there, this case has already been addressed in 2025.1. Here's the excerpt from the change log: • Changed the default compatibility level for new SQL databases created during the installation of the WEBCON BPS platform. As a result, the previous compatibility level set to 120 (SQL Server 2014)

Hello gentlemen, thanks for pointing out the issue. We're already working on a fix and it should be introduced to the product fairly soon :)