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.4 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Working Case Note | 20 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Working Case Note
The ability to add notes to a case is intrinsic to the functioning of most case management tools, and crucial for audit.
Notes roll up to the Case Key Value combination and are therefore available across all historic case records.
The presentation of data by Case Key and Case Key Value is of profound importance to ensure that a true history is maintained and evidential, rather than on a Case Id (as a case may cycle a number of times over the life of a Case Key and Case Key Value, thus having several Case Id).
Navigate to a case record via either Fetch or Skim:
Note the Case Notes tab:
Click on the Case Notes tab:
Case Notes are displayed in a grid from newest to oldest, by their creation date. Case Notes are comprised of the following:
| Name | Description | Example |
|---|---|---|
| Note | A free text note or memo. | Ask for kyc. |
| Priority | The allocated priority for the memo. Priority provides for an element of structure in otherwise unstructured, free text, data for the purpose of reporting. | High |
| Action | As created in Administration >> Cases >> Cases Workflows Actions. Actions provides for an element of structure in otherwise unstructured data while also providing automation capability via the Notification and HTP endpoint functionality. | High |
To add a new Case Note, observe the button Add new record, noting that it is disabled without input:
Start by typing into the note:
Note that the the Add button is now available to commit the new memo:
In this example, set the priority to High:
Set the Action to the only available value in the drop down, being the Cases Workflow Action set up in previously:
Click the Add Note button to commit the memo (cancel would abandon the template):
To assure a reliable audit, it is not possible to update or delete a Case Note. Upon an error being made, a new Case Note must be created annotating a correction to a previous entry. It is of course possible for a memo to be deleted at the database level, but this is STRONGLY discouraged as it compromises audit integrity of the case management system.