mirror of
https://github.com/hanzoai/jube-fork.git
synced 2026-10-30 18:33:33 +00:00
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.
5.5 KiB
5.5 KiB
layout, title, nav_order, parent
| layout | title | nav_order | parent |
|---|---|---|---|
| default | Main Menu Navigation | 2 | Navigation |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Main Menu Navigation
Navigation in the Jube platform is centred around a Menu, where each Menu item will redirect the user to a specific page to administer Jube:
In the above example, navigating to the Request XPath screen would be referred to as Navigate to Models > References > Request XPath, navigating firstly to the Entity Models menu item, Then, the References sub menu item and finally clicking the Request XPath sub menu item.
In this example the Request XPath page has been used, however, there are many pages which are navigated to in a similar manner. The functionality of each page is detailed individually in this documentation.
Upon clicking on the menu item, in this case Request XPath, the page will be redirected away to the Model Request XPath page:
The Main Menu Navigation is:
| Title | Description |
|---|---|
| Cases | Cases is the case management system that can output work to end users, as the result of Activation rules having matched. |
| Suppression | Suppression allows an end user, for example a customer service agent, to stop Activation Rules triggering for a given entity, for example an account number. Suppression allows for the removal of data from activation without necessitating the updating of the underlying Activation Rule. Suppression is an alternative to Lists. |
| Lists | Lists are components of Gateway, Activation, Abstraction Calculations, Inline Functions and Abstraction rules that allow the lookup of values, such as deny lists. |
| Dictionary | Dictionary are key value pairs that allow the real time lookup of values based on a key, returning a float value. An example of a dictionary key value pair would be the lookup of custom credit limits based on an account identifier. |
| Models | The specification of models in Jube. Examples of models might be Fraud Prevention, Advertising Technology, Credit Risk Analysis and Intrusion Detection. One example concept is that data is aggregated around an Entity identifier, such as an Account number. The models menu item will reveal a large amount of configuration sub menu items documented separately. |
| Visualisations | Visualisation allows for the presentation of reports which have been created in the Administration >> Visualisation pages. These reports are configured in the administrative section ofJube, allowing end users can retrieve reports on a self-serve basis under their existing authentication and authorisation. |
| Sanctions | Sanctions allows the manual lookup of names against multi part strings (e.g. ROBERT MUGABE) stored in Jube. Sanctions are supported on a real-time basis, direct API and manual basis. |
| Watcher | The Watcher is a real-time streaming interface showing instances of transaction or events having matched upon an Activation Rule. If a Latitude and Longitude is configured and available in Request XPath, the event will be plotted to the map using the colours specified in the rule. |
| Administration | Access to the administrative functions such as Authentication (Users), Authorisation (Roles and Permissions), Visualisation, Tenants and thread monitoring. |
As with the Menu Navigation section of this documentation, navigating through the platform headlines is a simple matter of clicking on the menu item. In the following example, Lists:
Clicking on the Lists will simply return the page as is common through all headings:
