Michal Rykiert

It lands straight into the backlog, I'm changing the status accordingly.

From the UX perspective I'm all for it. However, there's also the development side and an associated cost/effort required. The latter is the largest obstacle, as we need to keep the whole UI consistent across all supported platforms, screen resolutions, sizes, ratios, etc. When it comes to systemi

Paweł, we've improved the description of constants in the documentation. Let me know if it helps.

WEBCON does not offer OOTB offline capabilities for multiple reasons, but the most important is the loss of flexibility in modifying applications. However, companies that require offline data synchronization often use third-party solutions and then integrate them with WEBCON. For instance, I've he

Will do. Straight to the backlog.

It's not easy, but we'll look into it. I'm changing the status to "under review"

Since there's an update and solution, I'm closing the thread.

Right now we're not planning any major modifications into the permission system. We might re-visit this thread should more similar requests appear.

We'll do it :). Straight to backlog!

We'll address your scenario alongside other form-related project in the future. I'm labeling the thread as "not now", but stay tuned to updates about forms :)

We're working on introduction of "task forms" that should address your scenario. So as such, I'll label your thread as "not now", but keep in mind the solution should come from a slightly different angle :)

Sounds good -> backlog :).

This option will be enabled alongside with introducation of grid-based placement within dashboards.

We'll take it into the account along with other form-related development project. I'm putting it into the backlog.

Right now these kind of changes are out of our horizon, although we may re-visit the idea given more voices like yours are raised.

We'll fix it :). Straight to the backlog!

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.