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.7 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Visualisation Recall | 1 | Visualisations | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Visualisation Recall
Jube provides a rudimentary reporting tool that exists to execute SQL against the database and presenting as either a grid or visualisation. The philosophy is to make the creation of reports quick given a rudimentary understanding of SQL and the Kendo JQuery charting library (passed as JSON like Javascript fragments).
Visualisations are available for recall via the Visualisation Directory or the Case page. There are two default reports available respectively.
To view a report in the Visualisation Directory, navigate to the Visualisation page in the parent menu:
On click, a list of all Visualisations Registry entries toggled to display in the Visualisation Directory will be shown:
Clicking on the link, in this case ExampleVisualisation, will expose the Visualisation parameters:
Complete the parameters and click Run, in this case using the defaults:
There are two tiles, which are referred to as datasource's, which exist inside a canvas of a set width and height. The use of datasource's in this manner allow for the creation of dashboards.
In the event that the Visualisation is recalled instead from the case management page, parameters are not exposed, instead the report will recall matching parameters to the case payload. A Visualisation is allocated to a Case Workflow in the Case Workflow configuration:
A Visualisation does not have to be available to the Visualisation Directory to be available to the Cases page, except the availability of parameters on a like for like basis (matching those between Cases Workflow XPath and the Visualisation Parameters) is required.
To expose an example report embedded in the Case page, navigate to a Case:
Note the Case Visualisation tab, which will reference the report that is configured alongside the Case Workflow:
The loading of the case has the same effect as clicking on the report via the Visualisation directory, except, it will not require manual input of the parameters, as these will be matched from the case payload. Clicking on the tab will expose the visualisation:
The practical use of a Case Visualisation is to produce a visual consolidation of the case, oftentimes referred to a dashboard.