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.
3.1 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Visualisation Registry | 2 | Visualisations | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Visualisation Registry
Think of a Visualisation Registry as a report. The Visualisation Registry can have many Datasource's which share a common set of parameters. The Visualisation Registry is the wrapper and specifies the the size of the canvass for the datasource's to be arranged. The registry entry also controls the availability of navigation to the Visualisation through the Visualisation Directory.
To create a Visualisation Registry, navigate Administration >> Visualisation >> Visualisation Registry:
To select an existing Visualisation Registry locate the link corresponding to the name:
Clicking on the link will expand the Visualisation Registry:
To return to the list, click the Back button:
To create a new Visualisation Registry click the New button:
On clicking the New button a page will be presented with empty fields for the creation of the Visualisation Registry:
The Visualisation Registry takes the following parameters:
| Value | Description | Example |
|---|---|---|
| Show In Directory | A flag indicating is the Visualisation is to be presented in the Visualisation page (otherwise available only in the Case page as embedded). | True |
| Columns | The number of columns that the Visualization Registry will be divided into for the purpose of arranging the Datasource's, or tiles. | 6 |
| Column Width | Given the columns having been specified, the size in pixels of each column. | 300 |
| Row Height | Rows are otherwise unbounded, however, like columns, have their size in pixels specified. | 300 |
Complete the page as follows and above:
Click Add to create a version of the Visualisation Registry:
Upon a new Visualisation Registry having been created, and noting that the Show in Directory having been selected, it will be available for recall. Clicking Visualisation from the main menu:
It can be noted that a new entry has been created:
Clicking on the new entry will expose a blank page however in the absence of parameters nor datasource's having been created for teh Visualisation Registry.