Your rules, without a release
DetectX® modules depend on business rules to enhance security, increase efficiency and detect both known patterns of risk and opportunity. Transaction Monitoring and Risk-Based Profiling use them as fraud filters. The Rule Designer is the interface where those rules are created, modified and removed, and it supports complex patterns, integration to external data sources and the dictionaries the rules reference.
What the Business Rule Engine does
Machine learning reaches what nobody has described yet. Rules carry the part of your policy that is already written down, and the two run together.
Define new rules
Author
Create and implement new rules or filters tailored to your own requirements, in the designer rather than through a change request.
Publish rule versions
Publish
Update and publish new versions of rules, scripts or tables, so the latest parameters are always the ones in use.
Create dictionaries
Reference
Develop dictionaries that serve as static data sources for your business rules or filters to reference.
Track versions
History
Maintain a history of all previous versions of rules, scripts or tables, which is what makes a rollback straightforward.
Export and import
Reuse
Export a business rule for use in a different context, or import one that was created elsewhere.
Manage access
Control
Admin users manage entitlements, controlling access to the entire interface or to specific rules by assigning ownership.
Where it is used
The rule engine is one part of the DetectX® core. These solution pages depend on it.
Solution
Business rules used as fraud filters to identify potentially conspicuous activity involving customers.
Real-time Transaction Monitoring
Solution
The same rule set applied to the stream as it arrives.
Solution
A flexible rule designer that lets compliance teams create, test and activate the custom rules behind risk-based profiling.
Solution
Fraud detection rules tailored to unusual high-risk behaviours, with client-specific criteria added to the detection engine.
Solution
Customisable workflows, escalations and audit-proof documentation in the alert viewer, configured rather than coded.
Common questions
The Rule Designer is where rules are created, modified and removed. The web-dev material puts it more directly: custom detection rules are created, tested and activated with no coding required, and client-specific criteria are added to the detection engine. Who in your organisation is allowed to author and approve a rule is a deployment question.
Admin users manage user entitlements and can control access to the entire interface or to specific rules by assigning ownership. Which of your roles hold those entitlements is settled at deployment.
A dictionary is a static data source that a business rule or filter references. The Rule Designer creates and manages them alongside the rules themselves, and publishes them as versioned tables.
The live page describes a streamlined layout for quick access, detailed properties and rule creation, and says nothing further. No captured screen shows it, so this page does not draw one. A demonstration is the honest way to see the designer.
No. Both run on the same core. Rules carry the policy you have already written; the models reach activity no rule describes.
Business Rule Engine · DetectX®
See a rule written, published and rolled back.
Book a working session on your own policy. Bring your questions about authoring, dictionaries, entitlements and version control.
- Versioned
- A history of every previous rule, script and table, with straightforward rollback.
- Portable
- Rules can be exported for use in another context, and rules built elsewhere imported.
- Alongside ML
- Rules and models run together on one analytics core.