richard-churchman 7e4850a4e7
Implemented role‑based data isolation for Case Management and Visualisation: ...
* Added role‑based data isolation across all entities related to Case Workflows and Visualisation.
* Introduced a common UI JavaScript widget for assigning roles to supported entities; updated existing JS components and generic CRUD logic to integrate the new widget.
* Added role‑permission tables and corresponding migrations, POCOs, repositories, controllers, DTOs, and validations for all in‑scope entities.
* Updated all end‑user queries to include joins through role allocations, enforcing data isolation for both Case Management and Visualisation.
* Included role allocations in preservation/backup logic to ensure they can be exported and restored correctly.
* Added documentation describing the isolation model and validation behaviour for Case Management and Visualisation.
* Renamed various architectural methods where ActiveOnly semantics now also imply role‑allocation filtering.
* Improved “no data found” handling on the case page to avoid appearing as though data is still loading.
* Updated the case query compilation routine to enforce role‑based isolation.
* Forced session cache invalidation via migrations to rebuild SQL with new filtering rules.
2026-02-04 13:42:31 +02:00
A major refactoring of the software to make model IDs less volatile between Import, Export, and Peek (comparison) of the model configuration environment. As part of the extensive refactor, most tables have been updated to include a GUID field, which is consistent across Import, irrespective of the IDs remaining volatile. The consistent GUID allows for the separation of production (i.e., Case, Transaction, and Counter data), Redis cache data and quasi-production data(i.e, Lists, Suppressions, and Dictionaries) from the configuration environment. Significant rework of Controllers, Repositories and POCOs to support GUID as an access path rather than ID.
2025-08-13 19:01:08 +03:00
2022-11-04 13:24:24 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2022-11-04 13:24:24 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
A major refactoring of the software to make model IDs less volatile between Import, Export, and Peek (comparison) of the model configuration environment. As part of the extensive refactor, most tables have been updated to include a GUID field, which is consistent across Import, irrespective of the IDs remaining volatile. The consistent GUID allows for the separation of production (i.e., Case, Transaction, and Counter data), Redis cache data and quasi-production data(i.e, Lists, Suppressions, and Dictionaries) from the configuration environment. Significant rework of Controllers, Repositories and POCOs to support GUID as an access path rather than ID.
2025-08-13 19:01:08 +03:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
A major refactoring of the software to make model IDs less volatile between Import, Export, and Peek (comparison) of the model configuration environment. As part of the extensive refactor, most tables have been updated to include a GUID field, which is consistent across Import, irrespective of the IDs remaining volatile. The consistent GUID allows for the separation of production (i.e., Case, Transaction, and Counter data), Redis cache data and quasi-production data(i.e, Lists, Suppressions, and Dictionaries) from the configuration environment. Significant rework of Controllers, Repositories and POCOs to support GUID as an access path rather than ID.
2025-08-13 19:01:08 +03:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
A major refactoring of the software to make model IDs less volatile between Import, Export, and Peek (comparison) of the model configuration environment. As part of the extensive refactor, most tables have been updated to include a GUID field, which is consistent across Import, irrespective of the IDs remaining volatile. The consistent GUID allows for the separation of production (i.e., Case, Transaction, and Counter data), Redis cache data and quasi-production data(i.e, Lists, Suppressions, and Dictionaries) from the configuration environment. Significant rework of Controllers, Repositories and POCOs to support GUID as an access path rather than ID.
2025-08-13 19:01:08 +03:00
2025-11-29 14:08:55 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2022-11-04 13:24:24 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
2026-02-04 13:42:31 +02:00
2025-11-29 14:08:55 +02:00
richard-churchman
7e4850a4e7