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.
1.8 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Working Activations | 17 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Working Activations
At the point a case is created a copy of the event is stored alongside the case record. In this event payload there is a list of the Activation Rules that were matched upon, stored in their order of priority and match. The Activations tab exists to write out these activations in a convenient form representing the one to many relationship that exist between transaction or event (one) and Activation (many), insofar as one transaction or event may have many matches:
Navigate to a case record via either fetch or skim:
Notice that in the case detail pane, there exists a series of tabs, noting specifically the tab titled Activations:
Click on the tab titled Activations:
The Activations tab presents the Activation Rules that have matched, in the order of Response Elevation descending, upon match, with the first match at the top, the last match at the bottom. Activation Rule processing, and thus priority of Activation, is on the basis of:
- Enabled For Response Elevation and;
- Highest Response Elevation First.
- Enabled for Case Management and;
- Highest Priority Status First.
- Enabled for Notifications.
- Enabled for TTL Counter Increment.
- Alphabetically on Activation Rule Name.
It follows, that on an Activation Rule matching, the order of rules matching will respect the above.
Activations will only be visible if the Visible flag has been set in the Activation Rule:
