For Categories, user now see the plain list, but it is expected to select Categories, Locations, Cost Center and OrgUnit with hiearachical picker

As part of the concept that all background tasks on the Server are executed by the Functional Worker process, the Workflow Engine module should be reworked to run on the Functional Worker.

Each Workflow Instance is executed in an isolated process, which initializes the Data Layer in minimal mode, runs the Workflow until the next persistence point, and then releases the process.

Workflows are executed in the .NET Framework Functional Worker.

Out of scope: Workflows authored in Workflow Designer and running in the .NET Core Functional Worker based on CoreWF.

During a phased rollout, new employees should be assigned to the new look directly instead of getting familiar with the old look only to then switch to the new one.

This could be another flag in the Global System Settings

as we remove smth customer had, they need to get smth instead

so we make Liited version of reports.dashboards avialable

all function comes wth subscriptions

with linited is meant - READONLy->checking report with drilldown

but not adding charts from grid or dashboards itself

I wanted to share an idea regarding the new dashboards. Currently, it’s not possible for multiple users to collaboratively edit a dashboard. This can be limiting, especially when teams need to jointly manage or adjust widgets and layouts.

It would be ideal if dashboards could support access control—allowing a defined group of users or a specific user group to edit and manage a shared dashboard. This would greatly enhance collaboration and reduce the need for duplication or manual coordination.