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.9 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Creating Case Workflows | 1 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Creating Case Workflows
A case workflow is a logical stream of work that an agent will be allocated to. For example, transaction fraud for the purpose of evaluating stolen debit cards might be slightly different in treatment from an anti money laundering workflow. Where work effort or agent teams are different, it make sense to break this into different workflows.
Start by navigating to Models >> Cases Workflows >> Cases Workflows:
Cases Workflows are subordinate to models given that the meta data has been constructed at the model level, henceforth a case workflow can only be a child of a model such that the payload created by the model can reliably be presented by the cases page.
Click on the top of the tree to create a new Cases Workflow for the Detailed Financial Transaction Model:
The parameters available are described as follows:
| Value | Description | Example |
|---|---|---|
| Name | The name of the workflow for end user navigation. | Fraud Prevention |
| Enable Visualisation | A flag indicating if this case should present a visualisation taking its parameters from the case payload. Visualisation is documented elsewhere. | True |
| Visualisation | The visualisation to present subject to Enable Visualisation being selected. | Example Visualisation |
Complete the page with the parameters as above and as follows:
Scroll down the page and click the Add button to create a version of the Cases Workflow:
For confirmatory purposes, navigate to the Activation Rule definition for Volume1DayUSDForIPOver100 in the main menu:
Scroll down to Cases switch, and toggle to true:
Click on the Case Workflow drop down, which will expose the available Case Workflow for which entries can be made:
Clicking on the new Cases Workflow will reveal it to be incomplete for the purposes of case creation, requiring also a Cases Workflow Status:
