richard-churchman
5f6bbe45f7
Major bug fixes relating to the Redis implementation in Reprocessing and Search Key Cache were identified and fixed as part of the rekeying development. Included functionality to stop the Exhaustive training. Fixed the Unsupervised learning functionality in Exhaustive Training. Embedded the Mock Data CSV data into a class to make it compatible with Docker without needing to modify the Dockerfile (i.e, build). Included a new table that stores training data to enhance support capabilities for Exhaustive. Reintroduced and validated the Multitenancy functionality. Postgres is now fully deprecated in place of Redis for cache, and all implementations of the Interfaces for Postgres have been removed. No migrations exist to support this deprecation, and Postgres as a cache is now wholly unsupported. Removed the Indexing background thread, as Redis does not require it, given that it is a key-value pair database. Created a RedisCommandFlag Environment Variable to support Fire and Forget write to Redis in Invocation. Implemented functionality to Export, Peek and Download configuration environments using a secure, encrypted scheme. Created a permission to access the functionality via the user interface. Extensive database-based logging is included to provide for a comprehensive audit. Created functionality to Import the encrypted Export file inside a database transaction to ensure consistency. As Docker is now the primary deployment model, log4net instantiation has been moved to an approach that primarily uses programmatic instantiation of the ConsoleLogger and RollingFileAppender given Environment Variables. Implemented functionality to support remote \ mounted Log4Net XML Serialisation files for more advanced log4net configurations. Reintroduced access to counters via the user interface and created a permission. Took the opportunity to implement ReSharper linter suggestions. Disabled the Lock button across the whole application, with that functionality being reserved for future use. It is intended that locking happens programmatically on the basis of dependencies in future commits. Fixed several significant end-use bugs which became apparent during testing of the refactored code relating to case management and visualisations. Fixed certain other minor bugs that came up during testing. Brought documentation up to date for this commit. Brought the Docker Compose file up to date for this commit. Removed Redundant Environment Variables for this commit. Made the README file less verbose and unnecessary.
2.9 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Permissions | 3 | Administration | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Permissions
Permissions grant access to resources in the user interface, typically pages. Permissions are added to Roles, and then a Role is allocated to a user.
In practice, it is unlikely that a user with day to day responsibilities in customer services would require access beyond Case Management, Lists, Dictionary or Suppression. Similarly, an analyst that has responsibility for the creation of rule and reports is unlikely to need access to those pages enjoyed by customer service.
In the absence of a permission the user will not be able to navigate given absence of the resource in the menu. In the event of deep linking to a resource without a permission, an unauthorised http status code will be returned.
The Administrator role is created during migrations and has all available permissions allocated. To view permissions for the Administrator role, start by navigating Administration >> Security >> Permissions:
Locate the triangle to bring about an expansion of the tree, to expose the permissions for the Administrator role:
Click to expand permissions for the Administrator role:
Locate the Read Write Case permission for the Administrator:
Click on the Read Write Case permission to expand on the properties:
Deleting this permission will render the Case pages inaccessible:
Locate the Delete button:
Click the Delete button and confirm:
Refreshing the whole page will construct the menu without the Case menu item for absence of permission:
To establish the permission once again navigate to back to Administration >> Security >> Permissions, and click on the top on the tree node Administrator to create a new entry:
To add a permission is to select the permission from the drop down of available permissions. Locate the permissions drop down:
Select Read Write Case and ensure Active:
Click Add to create a version of the permission:
As permission may not be added twice. In the event the permission has already been allocated to the Role, the existing entry will be updated for the new properties. With the permission resetablished to access the Cases, a refresh of the whole page will make available the menu item:
