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.
7.2 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Working Case Event Journal | 21 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Working Case Event Journal
The Case Note relies on specific intervention by an end user or analyst to create an audit trail.
The elective Case Note approach to an audit trail is risky for the purposes of maintaining audit integrity. To assure audit integrity, Jube maintains a very detailed audit trail of all interactions in for a case record including the following events:
| Value | Description |
|---|---|
| Automatic Unlock | The case has been unlocked by an automated background process. |
| Skim Case | The case was opened via the Skim functionality. |
| Automatic Lock | The case was locked automatically as part of the automated Skim functionality. |
| Full Case Fetch | The case was fetched. |
| Closed | The case was closed. |
| Manual Lock | The case was manually locked. |
| Diary | The case was given a new diary flag. |
| Status Change | The case was given a new status. |
| Diary Date Change | The case was given a new diary date. |
| Rating Change | The case was given a new case rating. |
| Suspend Closed | The case was given a suspend closed status. |
| Suspend Open | The case was given a suspend open status. |
Navigate to a case record via either Fetch or Skim:
Note the Case Events Journal tab:
Click on the Case Events Journal:
Case Events are displayed in a grid form, from newest to oldest by their creation date. Case events are comprised of the following information:
| Value | Description | Example |
|---|---|---|
| Event | As described above, the event that took place. | Status Change |
| Old Data | The data as before update. | DAMLCO |
| New Data | The data as after update. | AMLCO |
| User | The user that that initiated the audit. | Administrator |
| Created Date | The date and time stamp of the audit. | The date and time stamp of the event. |
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 and case key value history, the link allows for the navigation through the history of the case key and case key value.
As the tabs retrieve their information based on a Case Vey Value combination, only the case record contents will change over time, such as the event \ transaction payload.