Introduction to Ckrule Business Rules management System

1. Brief description

The Ckrule Business Rules Management System (BRMS) is a platform for integrated application storage, management, execution, and testing that allows organizations to define, deploy, monitor, and maintain the complex decision logic used by operational systems. Ckrule BRMS Extracts and manages decision logic independently of the core application code so that these decision logic can be easily understood, maintained, and reused across the organization.

The Ckrule brms consists of 4 parts:

The functional details of each part are as follows:

Level function	Two-level features	Description
Rule store	--	The repository allows rules to be placed outside of the core application code. It also allows decision logic to be managed as an enterprise asset, enabling easier understanding and updating of decision logic.
Rule management	Rule edit	You can add, modify, and delete rules. Configurable rules id, rule names, fields, editors, notes, etc.
Rule execution	Service Publishing	Supports publishing webservice, json or WCF format services. Provides monitoring after publishing the service, displaying information such as the last Call time, execution time, and so on.
	Apply audit	Save service invocation information, such as caller, call Rule name, call start time, execution time, call result, etc.
Rule test	--	Can be tested according to the rules ' input and output objects Different rules.

By placing rules outside the application code, business experts can define and manage decision logic. This reduces the time and effort required to update the decision logic in the production system and improves the Organization's ability to respond to changes in the business environment.

2. Introduction to the interface2.1. Login Screen

After you enter the user name and login password, you can log on to the system.

2.2. Rule Pack Management

Rule Pack Management uses a tree structure, the left tree can control the classification and the package, the classification can be created again. Use the Move Down function to modify the sorting order and right-click to modify the classification or rule pack.

When modifying a rule package, click the Browse button to re-select the rule point and click the Edit Rule Package button to edit the rule. Click Edit Rule Pack to eject the Ckrule Rule Engine editor. Once the edits are complete, save in the editor of the Ckrule Rule engine, the interface closes automatically, and then is confirmed at the current interface point to complete the modification.

Description of the interface controls

Field name	Description
Rule Pack	You can browse or edit a rule package.
Coding	External is used to invoke the unique encoding of the rule package and cannot be duplicated.
Name	The name of the rule, which is displayed in the other interface later.
Field	An input-output object, also called a business object model, that is extracted dynamically from a rule.
Describe	Some description of the rule pack.
Version	Indicates how many times the current rule has been edited.
State	Only rule packages that are in effect can be called.
Edit Type	Represents a type that can be edited in the rule data editing interface.
Sort number	The sorting of the current rule in the category.
Classification	Classification of rules.

Export rules

You can export rule packages and rule data, such as decision tables and customer rule pools, so that the rules are packaged as a whole.

Import Rules

Imports rules into the brms as a whole, containing the settings for rule data such as decision tables and customer rule pools. After importing, to prevent conflicts, the rule encoding is set to the GUID and the rule classification is cleared. The administrator needs to edit the rules again.

2.3. Rule release

The rule package is set to take effect before it can be published, and when it is published, the service start and end times are selected, and the service can be called only within this time interval. Service type Be sure to choose one,json means using JSON-formatted data for HTTP communication, support for all programming languages, and even JavaScript can send requests. WCF is limited to. NET WCF usage.

2.4. Rule Audits

The interface displays information about requests that call the service, suggesting that the feature is limited to special situations and that the general database design is difficult to handle if the number of calls is very large.

2.5. Rule Testing

Rule tests can simulate sending JSON data to the server side, while the server returns the impact package for a particular format.

2.6. Rule Data Editing

Rule data editing is used to edit the decision table and the customer rule pool, and after the rule package is completed, it can be compiled into a piece of code that can be run by the machine, but if you want to implement more powerful rule setting, the business people who are familiar with the business are also actively involved in the setup. Rule data editing is to provide some interface to the business experts to set up data.

Decision table data settings are well suited to simple and very many rules, while customer rule pools are adapted to complex rules writing. Business experts can use the rules Editor to write a large number of customer rules.

2.7. User Management

User management interface can maintain both administrator and operator roles, operator login, only the data set interface, other interface is not available.

Introduction to Ckrule Business Rules management System