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.1 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Case Workflow Macro | 9 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Case Workflow Macro
There are a multitude of functions in the case page for the purposes of updating and annotating a case. Each of these update functions have their own user interface controls. For example, to update the closed status, it is a simple matter of just changing the value in the status bar drop down:
The case page can be extended by Macros which may invoke various Javascript functions on the case page to automate a series of common click sequences to expedite the case working process for an analyst.
The case pages Javascript functions are undocumented. The documentation as follows serves only to illustrate the functionality in general term.
To create a macro, start by navigating to Models >> Cases Workflows >> Cases Workflow Macro:
Expand to the second level of the tree for a model, clicking on the Cases Workflow to create new Cases Workflow Macro:
The Cases Workflow Macro form takes the following parameters:
| Value | Description | Example |
|---|---|---|
| Javascript | Javascript that will be invoked upon a click of the icon button. Do not include script tags as this will be handled by the Case page via the onClick event and then the eval() function of Javascript. | alert('This is an example'); |
| Image | The image to be included in the image button. The name will represent the tool-tip of the button. | Image |
Complete the form as above parameters or as below (use any image):
Click add to create a version of the Cases Workflow Macro entry:
To invoke the Cases Workflow Macro, navigate to a case record:
Notice in the top left hand corner an image button has been created, which will contain the Javascript function payload:
To invoke the Cases Workflow Macro, simply click on the icon:
Keeping in mind that the alert is part of the Javascript, the execution on conclusion will be another alert to the effect of Done:
Macros become especially powerful when used in conjunction with the common HTTP Endpoint or Notification functionality.