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.2 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Case Workflow Action | 7 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Case Workflow Action
Case Notes provide a means to annotate cases and provide a history of the unstructured actions taken. Case notes by their nature are unstructured and cannot be reported upon. There are two structured data items that can be attached to a case note:
- Priority (High, Medium and Low) and;
- Action Codes which are configured rolling up to the Cases Workflow.
In addition to providing typing and structure to unstructured notes, Action Codes can also drive Notifications and integrations \ automation.
To create an Action Code, begin by navigating to Models >> Cases Workflows >> Cases Workflow Action:
Expand the first level of the tree and click on the model to start a new entry:
Actions are extremely basic in comparison to other child elements available to the case workflow, really only taking a generic parameter of Name and the common parameters to drive HTTP Endpoints of Notifications.
Complete the form as follows:
Scroll down and click the Add button to create a version of the Cases Workflow Action:
Navigate to a case:
To allocate the newly created Action, locate the Case Notes tab:
Click on the Case Notes tab to expose recent notes, and the ability to create a new entry:
Locate the text editor section to create a new Note:
Type into the text editor as required:
On typing, the Add Note button will be enabled:
Alongside the add button there is a drop down containing the newly created Cases Workflows Action:
Having set the values, click on the Add Note button to create the note:
Notice how the note had been added and the Action and Priority recorded alongside.