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.0 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Creating Status Elevation | 11 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Creating Status Elevation
Consider the scenario where a rule creates a case having allocated a status of FLD (First Line Defence) as a consequence of an velocity rule having matched. Thereafter, suppose a transaction occurs in a sanctioned country, which is of course a much higher risk event than a velocity having been breached. Status elevation is able to change the status in an upward, more severe direction, on rule match, yet not allow for the status to be changed to a less severe, downward direction.
Navigate to Models >> Cases Workflows >> Cases Workflow Status, navigating to the status First Line Review:
Note the Priority as being Ultra Low.
Navigate after to the status Reported Cases Workflows Status:
Note the Priority as being Ultra High.
To demonstrate the status elevation, identity a case key and case key value that is currently open in the status FLD by navigating to the cases page, navigating to the case workflow and selecting the case workflow filter All Open:
Navigate to Case Id 1:
Make a note of the Case Key Value from the status bar, in this case AccountId = Test1.
If the case exists in all but a closed status, another case may never be created for a Case Key Value combination. However, it is possible to raise the status code priority based on subsequent rule matches.
Navigate to Models >> Activation >> Activation Rules and navigate to the existing rule Case Creation:
Scroll down to the case creation parameters:
Change the Case Workflow Status Priority to Reported:
Scroll down and update a new version of the Activation Rule:
Synchronise the model via Entity >> Synchronisation and repeat the HTTP POST to endpoint https://localhost:5001/api/invoke/EntityAnalysisModel/90c425fd-101a-420b-91d1-cb7a24a969cc for response as follows, noting AccountId to Test1:
To test the status elevation, identity a Case Key Value combination that is currently open, in the status FLD, by navigating to the Cases page, then navigating to the case workflow, and finally selecting the case workflow filter All Open:
Notice for the cases grid that the case has been elevated to a High status from its original default status (as identified by a change in colour and upward classification of the Priority) or in expanding the case:
