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.3 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Creating Case Entry With Activation Rule | 4 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Creating Case Entry With Activation Rule
Revisit Activation Models Activation and Reprocessing in this documentation before proceeding.
To create a case record as a consequence of an Activation Rule match, navigate to the Volume1DayUSDForIPOver100 created beforehand:
Scroll down to Cases checkbox in the Activation Rule:
Check Cases to expose the options to create a case as a consequence of this Activation Rule matching:
For the time being, do not adjust the Bypass parameters, yet note that the default case creation parameters are the Case Workflow and Case Workflow Status created in the previous procedures.
The Case Key refers to the value that will be used to distinctly create the case, whereby the case creation integrity will be enforced on that key. For example, if a Case Key is AccountID, only a single case record can be created for for a Case Key Value combination, for a case workflow.
Select parameters as follows:
Scroll down the page and click Add to create a 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:
It can be seen from the response that the Case Creation Activation Rule has activated, which will have driven the creation of a case.
To view the created case, navigate to Cases:
If not already selected by session, click on a Case Workflow Filter to display open cases:
It can be seen upon matching, a case has been created.
