Ckrule Business Rule Management System Overview, ckrule Business Rules

Ckrule Business Rule Management System Overview, ckrule Business Rules
1. Brief Introduction

Ckrule Business Rule Management System (BRMS) is an integrated platform for storing, managing, executing, and testing applications, allows organizations to define, deploy, monitor, and maintain various complex decision-making logics used by the operating system. Ckrule BRMS is independent of core application code extraction and Management of Decision logic, so that these Decision logic can be easily understood, maintained, and reused across the entire organization.

Ckrule BRMS consists of four parts:

The functions of each part are as follows:

Level 1 Function	Level 2 Function	Description
Rule Storage	--	The repository allows rules to be placed out of the core application code. It also allows the decision logic to be used as an enterprise asset management to support easier understanding and updating of the Decision logic.
Rule Management	Edit rule	You can add, modify, or delete rules. You can configure the rule ID, rule name, field, modifier, remarks, and other information.
Rule execution	Service Release	Supports publishing services in webservice, json, or wcf format. After the service is released, monitoring is provided to display the latest call time, execution time, and other information.
	Application Audit	Stores service call information, such as the caller, call rule name, call start time, execution time, and call result.
Rule Testing	--	You can test different rules based on the input and output objects of rules.

By placing rules outside of 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 ability of the Organization to respond to changes in the business environment.

2. Interface introduction 2.1. login interface

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

2.2. Rule Set Management

Rule Set Management uses a tree structure. The tree on the Left can control categories and packages, and then create categories under categories. You can use the move up and move down function to modify the sorting order. Right-click to modify a category or rule set.

When you modify a rule set, click the Browse button to reselect the rule point and click the edit rule set button to edit the rule. Click Edit rule set to bring up the Ckrule Rule Engine editor. After editing, click Save in the Ckrule Rule Engine editor. The page is closed automatically. Click OK on the current page to complete the modification.

Interface Control description

Field name	Description
Rule Set	Allows you to browse or edit rule sets.
Encoding	The unique external code is used to call the Rule Set and cannot be repeated.
Name	The rule name, which is displayed on other interfaces.
Field	The input and output objects dynamically extracted from the rule, also known as the Business Object Model.
Description	A description of the rule set.
Version	The number of times the current rule has been edited.
Status	Only valid rule packages can be called.
Edit type	Indicates the types that can be edited on the rule data editing page.
Order Number	Sort the current rule in the category.
Category	Rule category.

Export rules

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

Import rules

Import the rule to BRMS as a whole, including the rule data such as the Decision Table and the setting of the customer rule pool. After the import, to prevent conflicts, the rule encoding is set to guid, And the rule category is also cleared. The administrator needs to edit the rule again.

2.3. Rule Publishing

The rule set can be published only after it takes effect. You must select the service start time and end time when releasing the rule set. The service can be called only in this time range. You must select one service type. Json indicates http Communication Using Json data. It supports all programming languages and even javascript to send requests. However, Wcf is only applicable to. net wcf.

2.4. Rule Audit

This interface displays the request information for calling the service. We recommend that you use this function only in special cases. If the number of calls is very large, the general database design is hard to cope.

2.5. Rule Test

Rule testing can simulate sending Json data to the server, and the server returns an affected packet in a specific format.

2.6. Edit Rule Data

Rule data editing is used to edit the decision table and the customer rule pool. After the rule package is complete, it can be compiled into code that can be run on a machine. However, to implement more powerful rule setting functions, the business personnel familiar with the business should also actively participate in the setup. Rule data editing provides some interfaces for business experts to set data.

The data setting of a decision table is very suitable for some simple and many rules, while the customer rule pool is suitable for complicated rule writing. Business Experts can use the rule editor to write a large number of customer rules.

2.7. User Management

The user management interface can maintain two roles: Administrator and operator. When an operator logs on, only the data setting interface is available, and other interfaces are unavailable.