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.1 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Working Case Journal | 19 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Working Case Journal
Only a single case record may exist for a Case Key Value combination, for a given case workflow. Only upon a case being non existent or in Closed status, for that Case Key Value, for a cases workflow, may a new case be created.
Given creation it is quite possible that there can be many cases for a Case Key Value combination, for the case workflow, created over time as cases move from open to closed in response to different events / transactions.
The Case Journal shows the case records, containing the same data as the status bar in the case page, in grid form. The Case Journal will contain all cases for a Case Key Value combination, for a case workflow, ever created.
The presentation of data by Case Key Value combinations is of profound importance to ensure that a true history rolling up to a Case Key Value combination is maintained.
Navigate to a case record via either Fetch or Skim:
Note the tab by the name Case Journal:
Click on the Case Journal tab:
The Case Journal is the case status bar in grid row form:
Given the grid nature, it follows that there can be many entries. Notice that the Case Id is a link:
The Case Id link, upon click, will load that case into the case page as if it were fetched or skimmed.
In the event that there are several cases for a Case Key Value combination history, the link allows for the navigation through the history of the Case Key Value combination.
As the tabs retrieve their information based on Case Key Value combination, only the case record contents will change over time, such as the event \ transaction payload.
The Case Journal serves to provide a reliable low level audit of the Case Key Value combination.